I'm thinking this is due to not using the -r in my WSDL2JAVA command to include my client repository? I added this and now I am getting the following: java.lang.IllegalStateException: No valid ObjectCreator found. Threads I have come across indicate that this error is caused by an incorrect version of the STAX jar, but it is the one that came with Axis2 1.1.1. My classpath does not include any jars that are not part of the Axis2 1.1.1 distribution. Any ideas? Thanks, Ted
________________________________ From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 3:04 PM To: [email protected] Subject: Axis2 Client Stub not Generating WS-Security Headers 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().ge tUserid()); options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties().ge tPassword()); 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
