Hi jdcmember,
am I interpreting your response correctly in that:
(1) I use JAX-WS wsimport tool to create the stub and type classes
(2) implement the endpoint interface
(3) package all this up in a war file and deploy it on jboss
My questions are:
- I will need to run the wstools utility somewhere as well, to generate the jaxrpc-mapping.xml and webservice.xml, right ?
- wstools is also going to generate its own wsdl file. What do I do with that file ? and should I also package my own wsdl file with the war file ?
- If not, then what do I do with my own wsdl file ?
- Have you seen any limitations with this approach ?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999624#3999624
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999624
Hi Thomas, thanks for the reply.
This link talks about the client side. I am referring to the server-side on how to implement and deploy the service when one starts out with a WSDL. The JBoss documentation does not seem to address this approach, as it seems to auto-generate WSDL and mapping files using wstools. Also it does not address how does one generate the type classes.
I would appreciate if I can get some pointers as we are currently evaluating if JBossWS is the right way for us to go.
thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999603#3999603
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999603