[
https://issues.apache.org/jira/browse/CXF-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357206#comment-16357206
]
Sergey Beryozkin commented on CXF-7640:
---------------------------------------
I guess it is doable but not sure how realistic it is.
One option may be to update Spring helper to check
PhaseInterceptorChain.getCurrentMessage() on whether
"org.apache.cxf.useSpringClassHelpers" is explicitly set to false, if yes -
then delegate to the 'basic' ClassHelper.
But this is such a rare case so it seems having all the runtime which depends
on Spring go via the 2 extra checks (get the current message 1st, if not null -
get the contextual message property and check if it is not null which in fact
will be null for most cases) seems a bit expensive.
The other option can be to consolidate on the same CXF version, I appreciate it
may not be easy but probably the right way forward...
if you'd like, please experiment with the 1st option and if it works - submit
PR for the team to review. Thanks
> Create a form to set the use of Spring in the classHelper on a per client way
> ------------------------------------------------------------------------------
>
> Key: CXF-7640
> URL: https://issues.apache.org/jira/browse/CXF-7640
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Osvaldo Pina
> Priority: Major
>
> The solution for CXF-6191 allows for configuration of the use of Spring in
> ClassHelper in a per vm way via System property. Would be nice to have a way
> to configure it in a per instance way (or, at least, in a per classloader way)
>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
