Thanks for the answer, I was about to post a question related to the client 
generation for the same WSDL.

As you mentionned in the bug report, yep, I saw while debugging that the soap 
headers, correctly "inserted" into the operation interface as parameters using 
wscompile features "donotunwrap,searchschema,explicitcontext" are not taken 
into account by the jboss WSDL parser which cause a conflict while processing 
passed parameters (org.jboss.webservice.deployment.OperationDescription) and 
SOAP client generation.

So, as I understand, it could be the same bug (?)

Thx.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919057#3919057

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919057


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to