[
https://issues.apache.org/jira/browse/FEDIZ-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545763#comment-13545763
]
Peter Schyma commented on FEDIZ-35:
-----------------------------------
Yes.
Something like:
{code:title=STSClientFilter.java}
...
private Bus bus;
...
public Bus getBus() {
return (bus != null) ? bus : BusFactory.getThreadDefaultBus();
}
public void setBus(Bus bus) {
this.bus = bus;
}
{code}
> Allow to use a custom CXF bus for IdpSTSClient
> ----------------------------------------------
>
> Key: FEDIZ-35
> URL: https://issues.apache.org/jira/browse/FEDIZ-35
> Project: CXF-Fediz
> Issue Type: Wish
> Components: IDP
> Affects Versions: 1.1.0, 1.0.1
> Reporter: Peter Schyma
> Priority: Trivial
>
> We are using Fediz IDP and CXF STS in an OSGi environment. Instead of using
> the war file of IDP we register the IDP filters via BundleActivator in order
> to add more customization and allow to dynamically exchange the login form.
> Therefore we also use the CXF version which is deployed in our OSGi container
> (CXF feature for Karaf). This works perfect until we deploy the STS part (or
> any other bundle that uses CXF).
> When we have two bundles which use CXF there is no default CXF bus per
> bundle. So it's unpredictable which bundles bus will become the default CXF
> bus in this setup.
> So my improvement request is to change the way how STSClientFilter retrieves
> the bus which is used to construct the IdpSTSClient instance. One possible
> solution for this would be to introduce a new field which contains the bus
> which should be used and to default to BusFactory#getDefaultBus if no other
> bus is set.
--
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
