Web Sign On Changes to UserLookup 1.4.9

4 posts 0 followers RSS feed

1. Nick Howes Staff Information & Digital

   #1 09:23, Tue 12 Aug 2008

   Hello, As of UserLookup 1.4.9 there have been some tweaks that will need some (minor) changes to your application for it to continue working. The main changes are * *UserLookup* is now an interface. * As a result, *UserLookup.getInstance()* is no longer available. You should be able to run a find-and-replace to change it to* UserLookupFactory.getInstance()* * The *UserResolver* interface is still available for compatibility, but you may want to use*UserLookup* instead if you are referring to *UserResolver * directly. The reason for making *UserLookup* an interface is to allow it to be mocked and proxied more easily (for profiling, logging etc), which some applications would like to be able to do. It should also make it easier to write unit tests. Nick
   0 likes
    
2. Nick Howes Staff Information & Digital

   #2 10:07, Tue 12 Aug 2008

   Re: Changes to UserLookup 1.4.9

   To anybody who was about to: hold off updating UserLookup for the moment as some further changes are needed to the SSO Client library to make them work together.
   0 likes
    
3. Nick Howes Staff Information & Digital

   #3 11:47, Tue 12 Aug 2008

   Re: Changes to UserLookup 1.4.9

   You can now upgrade to SSO Client 1.62 and UserLookup 1.4.9. As always, if you start getting errors saying a class is not found or is an unexpected type, you almost certainly have an old version of SSOClient or UserLookup lying around. Check inside the war file (which is where it should be) and any lib directories on the classpath. Even multiple copies of the same version can confuse Java so it’s best to just have one copy inside the packaged app. Downloads: http://ivy-repo/sso-client/sso-client-1.62.jar http://ivy-repo/userlookup/userlookup-1.4.9.jar
   0 likes
    
4. Nick Howes Staff Information & Digital

   #4 11:41, Thu 23 Oct 2008

   Re: Changes to UserLookup 1.4.9

   For anybody who did upgrade, one of the more recent updates rolled back this API change. So if you missed version 1.4.9, you shouldn’t need to make any code changes.
   0 likes