[
https://issues.apache.org/jira/browse/CXF-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Moritz Bechler updated CXF-5552:
--------------------------------
Attachment: CXF-5552.patch
A patch against trunk refactoring JAXBDataBinding, main changes:
- extract JAXB context initialization code to
JAXBDataBindingContextInitializer, split into more manageable methods.
- extract XML schema initialization code to JAXBDataBindingSchemaInitializer,
split into more manageable methods.
- move initializer configuration out of JAXBDataBinding into the appropriate
place.
- move builtin schema definition to BuiltinSchemas.
- add abstraction from CachedContextAndSchemas to allow for other context
creation and caching impls than JAXBContextCache.
So far I have kept all APIs intact and only marked some methods deprecated.
Except for two unit tests, which I fixed, these methods seem unused by CXF
code. Depending on your policy for API breakage for current trunk these could
be removed.
JAXBContextIntializer and JAXBSchemaInitializer might also deserve some love
but I don't think I can do that right now.
Except for some, most certainly unrelated, failures (multiple JMS related
fails, some dep issue in osgi/itests-felix, a JSON namespace issue in
rt/rs/extensions/providers, hanging in systests/jaxrs) tests look good.
By the way:
org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest.testWsdlWithInvalidSchema() is
locale dependant and failed here with a german system locale.
> Allow JAXBDataBinding initialization customization
> --------------------------------------------------
>
> Key: CXF-5552
> URL: https://issues.apache.org/jira/browse/CXF-5552
> Project: CXF
> Issue Type: Improvement
> Components: JAXB Databinding
> Reporter: Moritz Bechler
> Attachments: CXF-5552.patch
>
>
> We have some special requirements for perfoming JAXB context and XML schema
> initialization. Unfortunately the current JAXB databinding initialization
> routines and the dependent code are very resistant to overriding only certain
> aspects of them leading to a lot of copied code for us to maintain.
> I would like to step up to refactor this code if that isn't planned by
> anybody else. Any objections?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
