Hide Forgot
project_key: SOA CXF is not fully integrated with SOA-P 5.1. For instance a non-digest username token does not work properly. This is something that works with Native WS stack. The work on CXF JAAS integration has already been done but is not present in EAP 5.1 since it has been developed later.
Link: Added: This issue is related to JBWS-2210
Link: Added: This issue is related to JBWS-3028
Kevin, please take a look at this one. candidate for SOA 5.1.0
All I can do is confirm that this functionality is not present in the CXF integration but there appears to be other issues within CXF. I discussed this issue with Darran, he has a workaround for this but not one that should be included in the platform.
Writer: Added: dlesage
Link: Added: This issue depends JBPAPP-5764