Hi all.
According to the JAX-WS 2.0, when starting from wsdl at client side, there is a restriction about mapping style as below.
We cannot use "Wrapper Style" if an input wrapper element's name is different from the corresponding operation's name in the wsdl.
As for details, refer to the "2.3.1.2 Wrapper Style" chapter and see the (ii) criterion of the specification.
This topic has already been brought up as a part of forumID=46&threadID=1621
http://forums.java.net/jive/thread.jspa?forumID=46&threadID=1621
But I bring up this topic again because I want to get opinions of many people.
Usually, Wrapper Style is more convenient than Non-wrapper Style because developers don't have to use Wrapper Beans generated automatically.
I think that this restriction is not only needless but obstacle.
For example, we cannot use Wrapper Style in case two interfaces in the same namespace have operations with the same name.
Basically, names of wrapper elements in the same namespace must be different each other of course.
So in above case, either one of the two names of input wrapper elements must be different from the corresponding operation's name necessarily.
As a result, we cannot use Wrapper Style about one of the two operations.
And for example, we cannot use it in case two operations in the same namespace share one input wrapper element too.
In this case, the input wrapper element's name must be different from either one of the two operation's name.
I think that mapping style have no relation to input wrapper element's name.
So, it makes no sense that mapping style depends on whether input wrapper element's name is equal to operation's name or not.
What do you think about this specification?
To tell the truth, I've pointed this problem to the Spec Lead of JSR 224(JAX-WS 2.0 Specification) directly.
He says that it is impossible to change the mapping rules but it might be possible to add something to ignore the operation's name.
I think that there should be means to select Wrapper Style or Non-wrapper Style more flexibly.
But if it is impossible, at least, it is necessary to be able to ignore the operation's name.
In the first place, what does the above restriction derive from?
In the specification of WSDL 2.0 (now candidate recommendation), there are some rules for values of operation's style.
These rules are similar to restrictions for Wrapper Style of JAX-WS 2.0.
And some of these rules (IRIStyle-5031, MultipartStyle-5037, RPCStyle-5015) are equal to the above restriction.
For example, RPCStyle-5015 says, "The local name of input element's QName MUST be the same as the Interface Operation component's name."
For more details, refer to the chapter "4. Predefined Operation Styles" of the "WSDL 2.0 Part 2: Adjuncts".
Does the above restriction of Wrapper Style derive from these rules of WSDL 2.0?
In the same way as above, I am afraid that these rules of WSDL 2.0 will become obstacle too.
Please try above with GlassFish application server and confirm what happens.
Let me know what you think about this problem.
Thank you.