Hi Juerg That's a good improvement as it reduces the amount of container specific code. This would also allow to move the creation of the redirect URL to the FederationProcessorImpl.
I do have on my todo list to support publishing the WS-Federation Metadata document. This could be moved to fediz-core too as it is mainly based on the configuration file. You can raise a JIRA for the "services" component of CXF (https://issues.apache.org/jira/browse/CXF) and attach the patch there (svn diff) or attach the patch in this mail thread. Thanks a lot. Oli ------ Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com ________________________________________ Von: Juerg Portmann [[email protected]] Gesendet: Mittwoch, 21. März 2012 11:05 Bis: [email protected] Betreff: FEDIZ container agnostic configuration Hi all At the moment all configuration is within the fediz-tomcat module ant thus has to be implemented for each container separately. I would propose to extract the common configuration part into an xml based configuration bean and move this to the fediz-core module. As addition, the configuration should be able to provide values for different target url's to add the possibility to support different scopes (container level, servlet context) I would like to contribute this functionality, what is the best approach to do so ? - Juerg
