Matthieu Ghilain created JUDDI-937:
--------------------------------------
Summary: PolicyRoundRobin not working without service cache
Key: JUDDI-937
URL: https://issues.apache.org/jira/browse/JUDDI-937
Project: jUDDI
Issue Type: Bug
Components: juddi-client
Affects Versions: 3.3.1
Reporter: Matthieu Ghilain
Priority: Minor
I use the following method in order to resolve an endpoint:
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
