Client endpoint address

[kcochrane]

Hello,
I am currently developing an application which requires to implement endpoints for some services and act as clients for others. Using 4.0.4 and ws import, I have both client and server components running correctly. In order to get the client to work the value of the wsdl location had to be specified in the wsimport task (which ultimately gets set as the constant WSDL_LOCATION in the service class). The only way I could get this to work was to define this as a location on the file system and then modify the address element in the wsdl file at that location. Can it be set up so that the client application is provided with a url dynamically at run time and it simply looks there for the wsdl? I do not want to place this url in the wsimport task as that happens at compile time and is a different url depending on deployed and testing environments. It would not be so bad if the location of the wsdl file provided to wsimport could be relative to the root of the deployed application but it only seemed to work when the full path was specified.
It looks to me as if I have missed something and am not quite doing things the right way as this method of locating an endpoint does not seem to make a lot of sense.
If anyone could offer some advice on the correct way to define the url for locating the endpoint it would be most helpful.

[thomas.diesler]

This is an FAQ

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting

[thomas.diesler]

Your ejb3 endpoint is probably not recognized as a WS endpoint. Is the deployer interceptor enabled? Do you have the @WebService annotation?

 <!--
 A deployer service for EJB3 endpoints.
 -->
 <mbean name="jboss.ws:service=WebServiceDeployerEJB3" code="org.jboss.ws.server.WebServiceDeployerEJB3">
 <depends-list optional-attribute-name="Interceptables">
 <depends-list-element>jboss.ejb3:service=EJB3Deployer</depends-list-element>
 </depends-list>
 </mbean>

[kcochrane]

Thank you for your reply.

The service endpoints are functioning fine, I have used the @WebService annotation successfully. My concern is with the way the client is working.

After a bit of closer examination of what I am doing, I would like to ask does 4.0.4CR2 support jax-ws style generated classes? That is classes generated using the wsimport tool, where the class used for finding the service extends javax.xml.ws.Service. The reason I ask is that in order to support these I have copied the libraries from jwsdp2.0 in to the application. Our application requires to use the wsimport javax.xml.ws style rather than the wscompile javax.xml.rpc one.

[thomas.diesler]

does 4.0.4CR2 support jax-ws style generated classes

Not, yet

http://jira.jboss.com/jira/browse/JBWS-644