Honestly, I’m not sure it’s at all possible. During security processing, the “body” has not been read yet due to the fact that the body may actually be encrypted or similar. Thus, the message contents and such that would make up the service parameters would not be available.
With CXF 2.x, you could make sure the SAAJInInterceptor is configured and then get the SAAJ model out of the contents and look at the body via the SAAJ API’s to extract stuff manually. However, that may stop working with 3.0 as we flip to a more streaming way of handling all of this. Dan On Jan 9, 2014, at 12:33 PM, Faz <[email protected]> wrote: > > Hi, > > I'm trying to procure the incoming message object inside the > verifyPlaintextPassword method, but unfortunately am not able to get that. > By incoming message I mean the service parameters that is set i the web > services wsdl file. > > Have tried the following but nothing seems to work, > > > the requestList above seems to be null always, but when I do the same in the > HandleMessage() of any interceptors it works fine. > > PLEASE let me know like how can i gain access to this object in the > validator class. > CXF version :2.6.9 > Thanks > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Message-Object-in-UsernameTokenValidator-tp5738424.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
