Grouper Developers Forum

[Chris Hyzer <>]

This is fixed:

 

https://bugs.internet2.edu/jira/browse/GRP-402

 

The problem was that the Grouper Web Service version used to be a Java enum.  If the server was 1.5.2, and after that was released, a client for 1.4.4 was released, then that client wouldn’t be recognized in the 1.5.2 server.  Though, it should be allowed for the 1.4.4 client to communicate with the 1.5.2 server.

 

This is done. There is no more grouper service enum for versions. It all uses the GrouperVersion class to parse and compare versions.

If the client has greater version than the server (only considering major and minor version, not considering build number or release candidate number), then there will be a warning returned to the client, but the operation will still be allowed to (attempt) to take place.

 

Here are examples of what we want  (again, if there is an F response, that just means give a warning to the client with the normal response)

    //client -> server -> ok?
    //1.5.2  -> 1.5.2     -> T
    //1.5.2  -> 1.5.1     -> T
    //1.5.1  -> 1.5.2     -> T
    //1.5.2  -> 1.4.0     -> F (released before 1.5.2)
    //1.5.2  -> 1.4.5     -> F (released after 1.5.2)
    //1.4.0  -> 1.5.2     -> T (released before 1.5.2)
    //1.4.5  -> 1.5.2     -> T (released after 1.5.2)
    //1.6.0  -> 1.5.2     -> F
    //1.5.2  -> 1.6.0     -> T
    //2.0.0  -> 1.5.2     -> F
    //1.5.2  -> 2.0.0     -> T

 

Regards,

Chris