cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CXF-5174) Split xkms into xkiss and xkrss parts
Date Tue, 27 May 2014 08:07:01 GMT

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

Christian Schneider closed CXF-5174.
------------------------------------

    Resolution: Won't Fix

> 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
>            Assignee: Christian Schneider
>
> 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.2#6252)

Mime
View raw message