You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (Created) (JIRA)" <ji...@apache.org> on 2012/01/27 11:18:40 UTC
[jira] [Created] (CXF-4069) JAXB DataTypeAdapter should be in its
own project
JAXB DataTypeAdapter should be in its own project
-------------------------------------------------
Key: CXF-4069
URL: https://issues.apache.org/jira/browse/CXF-4069
Project: CXF
Issue Type: Improvement
Components: JAXB Databinding
Reporter: Christian Schneider
Assignee: Christian Schneider
Fix For: 2.6
When using JAX-WS/JAXB it makes sense to use a custom binding config to create e.g. Date instead of XMLGregorianCalendar. These binding configs need type adapters. CXF provides such
an adapter in the tools common project. I think this is not the right place as it forces people to depend on the tools common project when the only thing they need is the adapter. This
is especially severe in OSGi where you might want to generate your stub code in its own project. Ideally this project should have no dependency to cxf at all.
Additionally there is the project that the optimized dependencies for cxf 2.6.0 do not have the tools common on the classpath. So the user would have to change thei project anyway.
So I propose to create a new project to host just the adapters. This allows people to only depend on this little project with no other dependencies.
--
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-4069) JAXB DataTypeAdapter should be in its
own project
Posted by "Christian Schneider (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved CXF-4069.
--------------------------------------
Resolution: Fixed
> JAXB DataTypeAdapter should be in its own project
> -------------------------------------------------
>
> Key: CXF-4069
> URL: https://issues.apache.org/jira/browse/CXF-4069
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.5.3
>
>
> When using JAX-WS/JAXB it makes sense to use a custom binding config to create e.g. Date instead of XMLGregorianCalendar. These binding configs need type adapters. CXF provides such
> an adapter in the tools common project. I think this is not the right place as it forces people to depend on the tools common project when the only thing they need is the adapter. This
> is especially severe in OSGi where you might want to generate your stub code in its own project. Ideally this project should have no dependency to cxf at all.
> Additionally there is the project that the optimized dependencies for cxf 2.6.0 do not have the tools common on the classpath. So the user would have to change thei project anyway.
> So I propose to create a new project to host just the adapters. This allows people to only depend on this little project with no other dependencies.
> We additionally should move rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringStyle.java and rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringBuilder.java there too.
--
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] [Updated] (CXF-4069) JAXB DataTypeAdapter should be in its
own project
Posted by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated CXF-4069:
-------------------------------------
Component/s: (was: JAXB Databinding)
Tooling
Description:
When using JAX-WS/JAXB it makes sense to use a custom binding config to create e.g. Date instead of XMLGregorianCalendar. These binding configs need type adapters. CXF provides such
an adapter in the tools common project. I think this is not the right place as it forces people to depend on the tools common project when the only thing they need is the adapter. This
is especially severe in OSGi where you might want to generate your stub code in its own project. Ideally this project should have no dependency to cxf at all.
Additionally there is the project that the optimized dependencies for cxf 2.6.0 do not have the tools common on the classpath. So the user would have to change thei project anyway.
So I propose to create a new project to host just the adapters. This allows people to only depend on this little project with no other dependencies.
We additionally should move rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringStyle.java and rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringBuilder.java there too.
was:
When using JAX-WS/JAXB it makes sense to use a custom binding config to create e.g. Date instead of XMLGregorianCalendar. These binding configs need type adapters. CXF provides such
an adapter in the tools common project. I think this is not the right place as it forces people to depend on the tools common project when the only thing they need is the adapter. This
is especially severe in OSGi where you might want to generate your stub code in its own project. Ideally this project should have no dependency to cxf at all.
Additionally there is the project that the optimized dependencies for cxf 2.6.0 do not have the tools common on the classpath. So the user would have to change thei project anyway.
So I propose to create a new project to host just the adapters. This allows people to only depend on this little project with no other dependencies.
Fix Version/s: (was: 2.6)
2.5.3
> JAXB DataTypeAdapter should be in its own project
> -------------------------------------------------
>
> Key: CXF-4069
> URL: https://issues.apache.org/jira/browse/CXF-4069
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.5.3
>
>
> When using JAX-WS/JAXB it makes sense to use a custom binding config to create e.g. Date instead of XMLGregorianCalendar. These binding configs need type adapters. CXF provides such
> an adapter in the tools common project. I think this is not the right place as it forces people to depend on the tools common project when the only thing they need is the adapter. This
> is especially severe in OSGi where you might want to generate your stub code in its own project. Ideally this project should have no dependency to cxf at all.
> Additionally there is the project that the optimized dependencies for cxf 2.6.0 do not have the tools common on the classpath. So the user would have to change thei project anyway.
> So I propose to create a new project to host just the adapters. This allows people to only depend on this little project with no other dependencies.
> We additionally should move rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringStyle.java and rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringBuilder.java there too.
--
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-4069) JAXB DataTypeAdapter should be in its
own project
Posted by "Christian Schneider (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196818#comment-13196818 ]
Christian Schneider commented on CXF-4069:
------------------------------------------
After talking to Dan we found more similar classes like org.apache.cxf.jaxb.JAXBToStringBuilder that also should be separate from the databinding.
As these classes are referenced by the code generated by the cxf xjc plugins it makes sense to move the runtime lib with the classes to xjc utils. So I will remove the jaxb-adapter project again and instead create a xjc-runtime project in xjc utils that will then contain all classes the code generators currently need.
> JAXB DataTypeAdapter should be in its own project
> -------------------------------------------------
>
> Key: CXF-4069
> URL: https://issues.apache.org/jira/browse/CXF-4069
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.5.3
>
>
> When using JAX-WS/JAXB it makes sense to use a custom binding config to create e.g. Date instead of XMLGregorianCalendar. These binding configs need type adapters. CXF provides such
> an adapter in the tools common project. I think this is not the right place as it forces people to depend on the tools common project when the only thing they need is the adapter. This
> is especially severe in OSGi where you might want to generate your stub code in its own project. Ideally this project should have no dependency to cxf at all.
> Additionally there is the project that the optimized dependencies for cxf 2.6.0 do not have the tools common on the classpath. So the user would have to change thei project anyway.
> So I propose to create a new project to host just the adapters. This allows people to only depend on this little project with no other dependencies.
> We additionally should move rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringStyle.java and rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBToStringBuilder.java there too.
--
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