Here's the answer to the web context question:
http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#JBossWS_Extenstions
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4046089#4046089
Reply to the post :
Hi!
I think this sounds terrible for you, but you probably have to start working in
the other direction. If you want to ensure your contract (the wsdl file) is
changed in the way you want, then you must start with taking control over it,
i.e. develop it by yourself. What I'm saying - take full
the package of complex parameters needs to be specified per java package within
a package-info.java file:
see http://www.jboss.com/index.html?module=bbop=viewtopict=103352
JBossWS 1.2.x generates buggy wsdl files, though unless
Thanks for the help guys. Turns out it was because I was using the jbossws
that was installed with jboss-4.0.5.GA, which i believe is version 1.0.3. I
guess jaxb bindings were not supported until a later version, because I
installed 1.2.1.GA and everything worked as expected.
However, I
Try using this at webservice bean level(at exposed method)
WebService(targetNamespace=)
WebParam(targetNamespace=)
WebResult(targetNamespace=)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4045564#4045564
Reply to the post :
Thanks for writing back.
That's actually the first technique I tried which also did not seem to work.
Here is an example of a my web service bean:
| @Stateless(name=VerificationWs)
| @WebService(
| name=VerificationWs,
| targetNamespace = VerificationWsBean.DEFAULT_NS)
|
