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

Matthieu Ghilain commented on JUDDI-941:
----------------------------------------

This is very helpful. I think that I can get this work using the approach you 
suggested with configuration file should work. I'll give it a try.

However I still think that this could interesting to resolved it automatically 
using JAX-WS runtime environment. Wouldn't it be possible to make a look-up in 
the JAX-WS context based on the service name provided by the \@WebService 
annotation to find the endpoint on which the service has been published or 
something like this?

> 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)

Reply via email to