Christian, That's probably not going to happen as we migrate over with all the plugins, providers and interceptors setup in the current environment to a better more decoupled design but still using CXF. I'm not even 100% positive I'm free of SOAP endpoints yet.
We a number of endpoints with different authentication mechanics and different logging requirements and that's why I'm trying to find a good way to implement and share bus configurations. I have one way of doing it via Blueprint that works and with the DS JAX RS I'll be working today on seeing if I can't create a standard mechanic for it that might have a number of defaults that can be set via cfg much like PAX JDBC. As an example, being able to enable/disable logging at the in/out interceptors would be nice. JAAS Authentication may be another. Haven't cracked it open yet. But I can easily bootstrap a similar component for SOAP if I needed using the same interface. I'm certainly wiling to be convinced that JAXRS Witeboard is more elegant if I see some compelling examples showing different security and logging configurations that snap into place for different use cases. Then I can sell it to my colleagues as a better way of refactoring the project. Honestly I've seen snippets and some examples of JAX RS Whitebaord but can say I never went "Wow! That's so cool. I have to use that...." That might be due to my lack of exposure or just that the samples weren't particularly overwhelming. -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
