cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (Closed) (JIRA)" <>
Subject [jira] [Closed] (CXF-3205) @XmlJavaTypeAdapter at package level versus ASM generation of wrappers
Date Tue, 08 Nov 2011 05:32:54 GMT


Freeman Fang closed CXF-3205.

> @XmlJavaTypeAdapter at package level versus ASM generation of wrappers
> ----------------------------------------------------------------------
>                 Key: CXF-3205
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: JAX-WS Runtime
>    Affects Versions: 2.3.1
>            Reporter: Benson Margulies
>            Assignee: Daniel Kulp
>             Fix For: 2.4.4
> 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 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 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message