[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019218#comment-17019218
]
Alex O'Ree commented on JUDDI-937:
----------------------------------
so my previous comments, while true, have nothing to do with the issue raised.
it looks like the usage of the cache is required for the roundrobin policy to
work currently. the javadocs are a bit parse but i think it uses the
subscription callback notification thing to register with juddi for changes to
a given business.
hmm...i think the simplest solution is to create a simple hashmap to act a
cache in this case. i also added a clear method to purge the cache if necessary.
[~ghila...@gmail.com] i know it's been a while, but would you mind looking at
the commit?
> 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
> Assignee: Alex O'Ree
> 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
(v8.3.4#803005)
