[CXF-3205] @XmlJavaTypeAdapter at package level versus ASM generation of wrappers

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.1
• Fix Version/s: 2.4.4
• Component/s: JAX-WS Runtime
• Assignee: Daniel Kulp
• Reporter: Benson Margulies
• Created: 19/Dec/10 22:18
• Updated: 08/Nov/11 05:32
• Resolved: 25/Oct/11 17:44

Description

If CXF just implemented the spec, users would need to create request and response wrapper objects for wrapped service methods. Users would know just what package those classes lived in, and could use @XmlJavaTypeAdapter on package-info.java to supply adapters for common types used in multiple methods as parameters.

CXF, however, has this nifty feature of auto-generating wrappers. The wrappers generate into a different package that the SEI/SEB. Further, for reasons that I have not debugged, putting a package-info.java into that auto-generated package, explicitly, does not work. Somehow, JAX-B does not see the package-info.class as appropriately associated with the wrappers.

It seems to me that it would make more sense that, if the SEI/SEB are in package 'x' (I think SEB makes more sense, but I'm not sure), and there is a package-info.class for the package, that it's annotations should be copied into the asm-generated package, such that JAX-B will see them.