[no subject]

2012-04-02 Thread Philippe A.
Hello, I have compiled Axis2 & rampart from trunk in order to workaround a bug with wsdl2java. The client I developed back with Axis 1.4.1 no longer works. More specifically, the username and password token does not get added by the client in the soap header (confirmed with tcpdump). Client reques

Re: [axis2 or rampart?] client not including username and password in header

2012-04-02 Thread Philippe A.
Sorry for the missing subject. I posted in a hurry. 2012/4/2 Philippe A. > Hello, > > I have compiled Axis2 & rampart from trunk in order to workaround a bug > with wsdl2java. The client I developed back with Axis 1.4.1 no longer > works. More specifically, the username and password token does n

Re: [axis2 or rampart?] client not including username and password in header

2012-04-02 Thread Philippe A.
I did a quick comparison of the generated code and found a few important differences. No wonder it does not work. No calls to attachPolicy in populateAxisService No call to _service.applyPolicy(); in ctor No generated function getPolicy It looks like I should have a look towards my policy / wsdl2

Re: [axis2 or rampart?] client not including username and password in header

2012-04-02 Thread Philippe A.
My problem seems to relate to UsernameToken assertion. Looks like this token cannot be used alone -- I oversimplified. It is the conclusion I draw after encountering the same issue with code generated in 1.4.1. 2012/4/2 Philippe A. > I did a quick comparison of the generated code and found a few