JAX-WS Detect and report duplicate wrapper classes
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-native-3.2.2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.3.0
From the JAX-WS specification section 22.214.171.124 regarding Document
Conformance (Default wrapper bean names): In the absence of customizations, the wrapper
class MUST be named the same as the method and the wrapper response bean class MUST be
same as the method with a "Response" suffix. The first letter of each bean name
is capitalized to follow
Java class naming conventions.
Conformance (Wrapper bean name clash): Generated bean classes must have unique names
within a pack-
age and MUST NOT clash with other classes in that package. Clashes during generation MUST
as an error and require user intervention via name customization to correct. Note that
some platforms do not
distiguish filenames based on case so comparisons MUST ignore case.
However if two services in the same package have the same operation there is an overlap of
the generated wrappers which then causes the schemas between the two WSDLS to overlap.
Using the @RequestWrapper and @ResponseWrapper annotations does separate the wrappers
which also corrects the WSDLs, from the JAX-WS spec 'Conformance' paragraphs above
this conflict should have been identified and reported as an error during deployment.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira