[CXF-5174] Split xkms into xkiss and xkrss parts

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Estimated Complexity: Unknown
• Assignee: Christian Schneider
• Reporter: Christian Schneider
• Created: 02/Aug/13 08:01
• Updated: 27/May/14 08:06
• Resolved: 27/May/14 08:06

Description

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.

Issue Links

• is related to: CXF-5173 Allow to enable or disble xkrss Operations for xkms