[
https://issues.apache.org/jira/browse/CXF-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173579#comment-14173579
]
Sergey Beryozkin edited comment on CXF-5552 at 10/16/14 9:37 AM:
-----------------------------------------------------------------
Right, I looked at the code, the reason it was done there was that it was the
only way to 'customize' JAXBDataBinding.initialize(), there it first checks
getServiceInfos() and then proceeds to getNamespaceToUse()...
I've no problems with updating JAXRSServiceImpl to set this property somewhere
else if needed...
Sergey
was (Author: sergey_beryozkin):
Right, I looked at the code, the reason it was done there was that it was the
only way to 'customize' JAXBDataBinding.initialize(), there it first check
getServiceInfos() and then proceeds to getNamespaceToUse()...
I've no problems with updating JAXRSServiceImpl to set this property somewhere
else if needed...
Sergey
> 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-2.patch, 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.3.4#6332)
