[JUDDI-937] PolicyRoundRobin not working without service cache

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.3.1
• Fix Version/s: 3.3.8
• Component/s: juddi-client
• Labels: cache juddi policy
• Assignee: Alex O'Ree
• Reporter: Matthieu Ghilain
• Created: 27/Oct/15 09:08
• Updated: 01/Feb/20 02:21
• Resolved: 01/Feb/20 02:21

Description

I use the following method in order to resolve an endpoint:

Resolve endpoint function

 private String resolveEndpointForServiceID(String uddiServiceId) {
        try {
            UDDIClient uddiClient = new UDDIClient();
            ServiceLocator serviceLocator = uddiClient.getServiceLocator("uddiv3");
            serviceLocator.setPolicy(PolicyRoundRobin.class.getName());
            return serviceLocator.lookupEndpoint(uddiServiceId);
        } catch (Exception e) {
            throw new EndpointResolutionFromUDDIException("Could not resolve endpoint '"+uddiServiceId+"'.", e);
        }
    }

I have registered two different binding templates in juddi. Using this code I always receive the same endpoint. This comes from the fact that the topology is reloaded each time the lookupEndpoint is called because there is no cache. I guess that the service policy should still be able to make a round robin between the binding templates even if no cache is used.