Is there any other way to pass header information through to the bus? Is this the same for transactions or reliable messaging as it is for security (all of transaction/security/rm is handled from an external endpoint to the binding component only)?
Freeman Fang-2 wrote: > > Hi, > > We don't support getting security context from the normalized message so > far, since ws-security is based on soap binding , but the normalized > message used for service pojo inside cxfse is based on jbi binding. All > ws-security feature is handled in cxf-bc, which means we support > ws-security between endpoint outside jbi container and the cxf bc, but > not inside jbi container. > > Best Regards > Freeman > > > depstei2 wrote: >> Once the cxf-bc has authenticated an incoming message, the message is >> sent to >> my cxf service engine. How does one go about getting the security >> context >> from the normalized message if the headers are stripped out? In >> standalone >> cxf, you can grab the wsContext inside your service implementation pojo. >> Is >> there a way to inject the cxfse wsContext into your service pojo? >> >> > > -- View this message in context: http://www.nabble.com/CXF-Security-context-tf4817408s12049.html#a13794368 Sent from the ServiceMix - User mailing list archive at Nabble.com.
