[prev in list] [next in list] [prev in thread] [next in thread] 

List:       scout-dev
Subject:    [jira] [Commented] (JUDDI-941) Dynamic discovery of web service endpoint
From:       "Alex O'Ree (JIRA)" <juddi-dev () ws ! apache ! org>
Date:       2015-11-26 2:31:10
Message-ID: JIRA.12913069.1447501616000.198961.1448505070983 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/JUDDI-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028046#comment-15028046 \
] 

Alex O'Ree commented on JUDDI-941:
----------------------------------

brain storming here, can you try adding the settings to system properties before \
starting the UDDI Client.

> Dynamic discovery of web service endpoint
> -----------------------------------------
> 
> Key: JUDDI-941
> URL: https://issues.apache.org/jira/browse/JUDDI-941
> Project: jUDDI
> Issue Type: Improvement
> Components: juddi-client
> Affects Versions: 3.3.1
> Reporter: Matthieu Ghilain
> Labels: SOAP, discovery, dynamic, endpoint, juddi
> Original Estimate: 72h
> Remaining Estimate: 72h
> 
> Here is the example from the JUDDI documentation:
> {code:title=HelloWorldImpl .java|borderStyle=solid}
> @UDDIService(
> businessKey="uddi:myBusinessKey",
> serviceKey="uddi:myServiceKey",
> description = "Hello World test service")
> @UDDIServiceBinding(
> bindingKey="uddi:myServiceBindingKey",
> description="WSDL endpoint for the helloWorld Service. This service is used for "
> 				  + "testing the jUDDI annotation functionality",
> accessPointType="wsdlDeployment",
> accessPoint="http://localhost:8080/juddiv3-samples/services/helloworld?wsdl")
> @WebService(
> endpointInterface = "org.apache.juddi.samples.HelloWorld",
> serviceName = "HelloWorld")
> public class HelloWorldImpl implements HelloWorld {
> public String sayHi(String text) {
> System.out.println("sayHi called");
> return "Hello " + text;
> }
> }
> {code}
> The problem with this kind of registration is that it is still static. The \
> accessPoint should be resolved dynamically at runtime. Otherwise it is not possible \
> to spawn new service instances dynamically and to scale. This in my opinion should \
> be part of the JUDDI features. What do you think?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]