Sanjay I think this approach would work much better with the Policy based config model for Rampart. You should be able to put the PWCallback class in the lib directory if you really want to separate it from the service code.
Paul On Jan 14, 2008 12:06 PM, Sanjay Vivek <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > I've a simple EchoService and I would like to keep the Password Callback > Handler classes separate for both the client and service. So what I did > was to edit my client.axis2.xml as shown: > > <parameter name="OutflowSecurity"> > <action> > <items>UsernameToken Timestamp</items> > > <user>wsuser</user> > > <passwordCallbackClass> > echo.PWHandlerClient > </passwordCallbackClass> > > <!-- > <passwordType>PasswordText</passwordType> > --> > </action> > </parameter> > > And I edited my services.xml as shown: > > <parameter name="InflowSecurity"> > <action> > <items>UsernameToken Timestamp</items> > > <passwordCallbackClass> > echo.PWHandlerServer > </passwordCallbackClass> > </action> > </parameter> > > How does client.axis2.xml know where to look for the PWHandlerClient > class? I put both the PWHandlerClient and PWHandlerServer classes in my > EchoService.aar. However, I'm getting the following exception when I > attempt to invoke the service: > > Exception in thread "main" org.apache.axis2.AxisFault: WSHandler: cannot > load password callback class: echo.PWCBHandlerClient; > > Where should I put the PWHandlerClient class? Any help would be > appreciated. Cheers. > > > Regards > -------------- > Sanjay Vivek > Web Analyst > Middleware Team > ISS > University of Newcastle Upon Tyne > -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com
