You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2013/08/02 10:03:49 UTC

[jira] [Updated] (CXF-5174) Split xkms into xkiss and xkrss parts

     [ https://issues.apache.org/jira/browse/CXF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider updated CXF-5174:
-------------------------------------

    Fix Version/s: 3.0.0
    
> Split xkms into xkiss and xkrss parts
> -------------------------------------
>
>                 Key: CXF-5174
>                 URL: https://issues.apache.org/jira/browse/CXF-5174
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Christian Schneider
>             Fix For: 3.0.0
>
>
> Currently xkms supports both xkiss and xkrss operations in the same code.
> As can be seen in the linked issue it often makes sense to only support xkiss.
> Currently we support this using a switch.
> A better way may be to separate the xkrss Operations into a separate bundle. This bundle will expose an internal service with the interface "org.apache.cxf.xkms.handlers.Register". 
> If the main service finds such an OSGi service it will forward xkrss methods to this service. If it does not find it it will return Sender / Message Unsupported. 
> This is much better than the current aproach where we use spring to wire in the xkrss Register handler as the user can change or remove the implementation without messing with the spring context.

--
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