Thanks for your assistance Ruchith. I was able to get it working. Thanks, Ted
-----Original Message----- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 2:34 AM To: [email protected] Subject: Re: Axis2 Client Stub not Generating WS-Security Headers Hi Ted, On 3/28/07, Ted Jones <[EMAIL PROTECTED]> wrote: > Thank you for the reply Ruchith. I am following these instructions > with the exception of the service invocation since I am using my > generated client stub. Does the client repository location need to be > included in order to generate the proper stub logic for inserting the > WS-Security headers? When you codegen the stub will *not* contain any logic related to rampart. > Also, the code sample links are broken on the link you gave me. The link is now fixed. Thanks, Ruchith > > Thanks, > Ted > > -----Original Message----- > From: Ruchith Fernando [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 27, 2007 11:04 PM > To: [email protected] > Subject: Re: Axis2 Client Stub not Generating WS-Security Headers > > Hi Ted, > > Please see this : > http://www.wso2.org/library/240 > > Thanks, > Ruchith > > On 3/28/07, Ted Jones <[EMAIL PROTECTED]> wrote: > > > > > > I have an Axis2 1.1.1 ADB generated client stub that is instantiated > > using a client axis2.xml config and pointing to a client repository > > that has the rampart and addressing mar files. The config file and > > repository location are loaded via URL. In debug, I can see the > > rampart and addressing modules are engaged. In my client code, I > > have added the following properties to the serviceclient's options > instance: > > > > options.setProperty(WSConstants.WSSE_NS , > > WSConstants.USERNAME_TOKEN_LN); > > options.setProperty(WSConstants.USERNAME_LN,getConnectionProperties(). > > getUserid()); > > options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties(). > > getPassword()); options.setProperty(WSConstants.PASSWORD_TYPE_ATTR, > > WSConstants.PASSWORD_TEXT); > > > > The WS-Security headers are never inserted into the soap request and > > I > > > receive the ever-popular "org.apache.axis2.AxisFault: WSDoAllReceiver: > > Incoming message does not contain required Security header". > > > > This web service and the ws-security logic works using soapUI (a > > great > > *free* tool by the way). > > > > Is there some other property I need to set in the options or > > something > > > else I need to be doing? > > > > Thanks > > Ted > > > > > > > -- > www.ruchith.org > www.wso2.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- www.ruchith.org www.wso2.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
