-
-
2. Re: Client endpoint address
thomas.diesler May 11, 2006 7:44 AM (in response to kcochrane)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>
-
3. Re: Client endpoint address
kcochrane May 12, 2006 6:35 PM (in response to 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. -
4. Re: Client endpoint address
thomas.diesler May 14, 2006 5:09 AM (in response to kcochrane)
does 4.0.4CR2 support jax-ws style generated classes
Not, yet
http://jira.jboss.com/jira/browse/JBWS-644