[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980253#comment-14980253
]
Matthieu Ghilain commented on JUDDI-937:
----------------------------------------
I don't understand very well your point to be honest, maybe I miss something
because I am still not really familiar with the code ;).
> 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
> Labels: cache, juddi, policy
>
> I use the following method in order to resolve an endpoint:
> {code:title=Resolve endpoint function|borderStyle=solid}
> 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);
> }
> }
> {code}
> 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)
