You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2012/11/19 13:36:58 UTC
[jira] [Commented] (DOSGI-11) dOSGi creates new databinding
instance instead of using a spring-loaded databinding if available
[ https://issues.apache.org/jira/browse/DOSGI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500199#comment-13500199 ]
Sergey Beryozkin commented on DOSGI-11:
---------------------------------------
User was expecting a CXF DataBinding configuration to be recognized by DOSGi - but in DOSGI it does not work, instead a new WS property, something like "org.apache.cxf.ws.databinding.configured" has to be introduced, given that "org.apache.cxf.ws.databinding" is already reserved, and this property will need to be handled same was as say "org.apache.cxf.rs.provider".
I'll reopen the issue and try to get it fixed before 1.4 is out
> dOSGi creates new databinding instance instead of using a spring-loaded databinding if available
> ------------------------------------------------------------------------------------------------
>
> Key: DOSGI-11
> URL: https://issues.apache.org/jira/browse/DOSGI-11
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Reporter: Ahmed Aadel
>
> It seems dOSGI doesn't look for the user spring-configured data binding instance but instead creates and uses a new one, leading to a faulty context with default properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira