[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027938#comment-17027938
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 13101ecb48ad76fbb3a8c4aee84852887aae340d in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=13101ec ]
Merge branch 'bug/JUDDI-937'
> 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
> Fix For: 3.3.8
>
>
> 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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027937#comment-17027937
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 5ac79c870c2e804ca154ee1dc207e6a8087d609d in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=5ac79c8 ]
JUDDI-937 adding test cases, discovered a caching mechanism that had no way of
being cleared which was resolved.
> 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
> Fix For: 3.3.8
>
>
> 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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027936#comment-17027936
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 07790a220657525c85d446ed9427aa9ac3fac6ee in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=07790a2 ]
JUDDI-937 this resolve the caching issue, needs a test case still
> 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
> Fix For: 3.3.8
>
>
> 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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019635#comment-17019635
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 5ac79c870c2e804ca154ee1dc207e6a8087d609d in juddi's branch
refs/heads/bug/JUDDI-937 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=5ac79c8 ]
JUDDI-937 adding test cases, discovered a caching mechanism that had no way of
being cleared which was resolved.
> 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
> Fix For: 3.3.8
>
>
> 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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019217#comment-17019217
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 07790a220657525c85d446ed9427aa9ac3fac6ee in juddi's branch
refs/heads/bug/JUDDI-937 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=07790a2 ]
JUDDI-937 this resolve the caching issue, needs a test case still
> 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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980286#comment-14980286
]
Alex O'Ree commented on JUDDI-937:
--
ok, i'll explain further...
> the lookupEndpoint only fires when the
> bindingTemplate/accessPoint/useType=endPoint (all other's are ignored, which
> is dumb IMO. The jUDDI REST endpoint handles other cases, why not this one?)
A business has 0 or more services. a service has 0 or more bindings. a binding
has 1 access point with that has a string for the value (usually the URL to the
service) and a string for the type. The type, according to the spec can be
"endPoint" which is where you execute the service, "wsdlDeployment" which means
use that for your client (or parse it for the actual endpoint), and
bindingRedirector and something else. The ServiceLocator.lookupEndpoint only
handles "endPoint" correctly. So if you've registered a service, the
business/service/binding/accessPoint/type has to be endPoint in order for it
work.
The REST endpoint does not have this limitation and will resolve the execution
endpoint of a service given the service key.
ServiceLocator.lookupEndpoint, without the cache, cannot use round robin since
there's (currently) no way to get the topology object out. If this is a need
for you, we can extend the code to make that part feasible.
> 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)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
