[
https://issues.apache.org/jira/browse/CXF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-5174:
-----------------------------
Fix Version/s: (was: 3.0.0-milestone1)
3.0.0-milestone2
> 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-milestone2
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
