You MAY be able to do this by writing a completely generic Provider<SOAPMessage> based service that just forwards onto another service. The security information would be set on that and the spring could configure in a URL to the service it then sends the SOAP messages onto. It would then use the dispatch APIs (or even the straight SAAJ apis I think would work if you are talking straight HTTP) to forward the SAAJ message onto the real server, get the SAAJ back, and return it where the security would do it's thing.
Dan On Monday 04 February 2008, [EMAIL PROTECTED] wrote: > Hello, > > I am working with CXF 2.0.4 with javaFirst/Spring/CXF Servlet. > I have the jaxws setup using Timestamp, Signature, and Encypt. > I have some customized interceptors and a handler. > > This is all included in one war file (just like the demos) that I > deploy to JBoss (and eventually Websphere). > > I was wondering if its possible to: > - separate out my service implementation as one war file and my > security configuration as another war file > or > - have my service endpoint be external from the same JVM that CXF is > under (the internal endpoint is different from the published external > endpoint). > > > The goal is to keep the security settings "untouchable" when further > maintenance/enhancements of the service methods goes forward. > We don't want to have to worry about the security getting broken once > we know that its working correctly. > > I believe that this is called "hardening" the security. > > Any suggestions/readings would really be appreciated. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
