Hi all.
According to the JAX-WS 2.0, when starting from java at server side without customizations, there are restrictions as below.
1. Two or more Service Endpoint Interfaces (SEIs) cannot have methods with the same name in the same package.
2. SEIs cannot have a method named "xxxResponse" when a method named "xxx" exists in the same package.
What do you think about this specification?
This topic has already been brought up as a part of forumID=46&threadID=13381.
http://forums.java.net/jive/thread.jspa?forumID=46&threadID=13381
But I bring up this topic again because I want to get opinions of many people.
Following two java classes are generated per method in a SEI, "Request Wrapper Bean" and "Response Wrapper Bean".
Request Wrapper Bean is generated of the same name with the corresponding method in the same package of the SEI.
And, Response Wrapper Bean is generated of the method's name + "Response".
So if there are SEIs that have methods with the same name in one package, Request Wrapper Beans will conflict.
In the same way, Response Wrapper Beans will conflict too.
And if there are methods named "xxx" and "xxxResponse" in one package, Request and Response Wrapper Beans will conflict.
As for details, refer to the "3.6.2.1 Document Wrapped" chapter of the specification.
To tell the truth, I've pointed this problem to the Spec Lead of JSR 224(JAX-WS 2.0 Specification) directly.
I suggested changing the default name of Request/Response Wrapper Bean to include SEI's name, and regarding Request, to append suffix such as "Request".
But he says that it is impossible to change the specification.
He says that with using Request/ResponseWrapper annotation, we can avoid these problems.
But I think that above name collisions must not occur even though without such annotation.
Normally, developers don't have to be conscious of Request/Response Wrapper Beans, because they are generated automatically.
So, I think that it is no problem to change the specification.
In the first place, is it all right about a specification that raises name collisions out of developer's conscious?
In my opinion, this is almost a bug of specification.
Please try above with GlassFish application server and confirm what happens.
Let me know what you think about this problem.
And present JAX-WS 2.0 has another problem that is related in part to the above problem.
It is true that we can avoid name collisions by using Request/ResponseWrapper annotation at server side.
But now at client side, things will be very inconvenient because of another restriction in the specification.
Actually, above name collisions are not only about Wrapper Beans but also about Wrapper Elements of WSDL.
As well as Wrapper Beans, Wrapper Elements in a WSDL must not conflict in the same namespace.
For more details, I will bring up as another topic.
Thank you.