No one know this?
Thank you very much!
But for the '-e', the commandline help say: it is for soap1.2.
Could we use it for soap1.1?
I think so, '-e' switch should tell the tool to generate portable artifacts from WSDL (SOAP 1.1) - if there's SOAP 1.1 binding defined in WSDL - and artifacts for tool supported extensions (SOAP 1.2, ...); use of '-e' may only result in non-portable apps
Also note that "wsconsume -e" should be same as or at least similar to "wsimport -extension"
Did you create the jira of jboss tools? What do you do? A user, jboss ws developer or a tester?
I feel that you are more familar with jboss ws than me.
Sorrry for my bad english, I don't catch your meanings. You said, the -e is ok for soap1.1 and soap1.2,
and if I use -e for all the scenes, it is ok. Right?
For example, just a wsdl include a portype and use soap1.1,
it will works correctly when we use -e?
I don't find the detail document for the wsconsume -e. -e means -extension, but a wsdl file include multi porttype, I think it is not a extension.
So I am puzzled with it.
Yes, I created that issue and I'm QE for JBTools/devstudio. I don't think I'm more familiar with JBossWS than you, I've been only working with JAX-WS spec/Metro (Sun's RI) since the spec became public and we've been solving the same issue (support WSDLs w/ more port types) in the other IDE.
Yes, using '-e' for all the scenes is IMHO the right thing to do on our side (that's also similar to how we solved it in the past...), basically it turns few particular errors only into warnings.
You are right that having more port types is not an extension but using other than SOAP 1.1 binding in WSDL is an extension. Particularly .Net services/WSDLs are often using SOAP 1.2, HttpGet and HttpPost bindings and one should use '-e' switch if he wants to ie create a client which supports all bindings.