[
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
