You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (Jira)" <ju...@ws.apache.org> on 2020/01/20 03:17:00 UTC
[jira] [Assigned] (JUDDI-937) PolicyRoundRobin not working without
service cache
[ https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex O'Ree reassigned JUDDI-937:
--------------------------------
Assignee: Alex O'Ree
> 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)