I dont know if i can help you much but i have exactly the same settings like you and made
some experiences.
@ 1) i have an own WebService running as EJB3 endpoint that uses a customized wsdl file.
That should be the same as to implement an already existing wsdl file. It proves that
JBoss does not need to generate its own WSDL file during deployment. You can get your WS
running by providing your own WSDL file.
@ 2) You can try JAX-WS wsimport tool to generate a Service Endpoint Interface out of your
WSDL file. Then you just have to implement it *in theory*. Wsimport works for me.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990102#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...