You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2010/12/19 23:19:00 UTC
[jira] Created: (CXF-3205) @XmlJavaTypeAdapter at package level
versus ASM generation of wrappers
@XmlJavaTypeAdapter at package level versus ASM generation of wrappers
----------------------------------------------------------------------
Key: CXF-3205
URL: https://issues.apache.org/jira/browse/CXF-3205
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 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Closed] (CXF-3205) @XmlJavaTypeAdapter at package level
versus ASM generation of wrappers
Posted by "Freeman Fang (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang closed CXF-3205.
-----------------------------
> @XmlJavaTypeAdapter at package level versus ASM generation of wrappers
> ----------------------------------------------------------------------
>
> Key: CXF-3205
> URL: https://issues.apache.org/jira/browse/CXF-3205
> 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 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3205) @XmlJavaTypeAdapter at package level
versus ASM generation of wrappers
Posted by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3205.
------------------------------
Resolution: Fixed
Fix Version/s: 2.4.4
Assignee: Daniel Kulp
> @XmlJavaTypeAdapter at package level versus ASM generation of wrappers
> ----------------------------------------------------------------------
>
> Key: CXF-3205
> URL: https://issues.apache.org/jira/browse/CXF-3205
> 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 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3205) @XmlJavaTypeAdapter at package level
versus ASM generation of wrappers
Posted by "Steven Swor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034874#comment-13034874 ]
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: https://issues.apache.org/jira/browse/CXF-3205
> 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 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira