cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Swor (JIRA)" <>
Subject [jira] [Commented] (CXF-3205) @XmlJavaTypeAdapter at package level versus ASM generation of wrappers
Date Tue, 17 May 2011 16:48:47 GMT


Steven Swor commented on CXF-3205:

Shouldn't this be considered a bug, since it breaks our ability to use the annotations at
the package level?

> @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
> 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.
For more information on JIRA, see:

View raw message