fixed the issue in both trunk and branch. please have a look at with a
nighly build.
Amila.
On 8/1/07, Amila Suriarachchi [EMAIL PROTECTED] wrote:
thanks, I could recrate the problem and looking into it. please put a
jira.
On 8/1/07, Mehar [EMAIL PROTECTED] wrote:
Hai Amila
I
Hai All,
I have a wsdl with a single service and many operations.
The typical payload for an operation will look like this
soapEnv:Envelope
soapEnv:Header
sessonId123123123141341/sessionId
source32312312312312/source
security
usernameToken
userNameafjlksdajflas/userName
I wrote a sample service which uses the Headers and it worked fine.
Can you please send your wsdl and Client?
Amila.
On 8/1/07, Mehar [EMAIL PROTECTED] wrote:
Hai All,
I have a wsdl with a singele service and many operations.
The typical payload for an operation will look like this
Hai Amila
I cannot give u my wsdl, did u try with a soap header with a single
element??
Code works fine with soap headers with multiple elements like
level1
level2/
/level1
My suspect is soapHeaderBlockSource565.addChild(
omElementSource565.getFirstElement ());
if the
thanks, I could recrate the problem and looking into it. please put a jira.
On 8/1/07, Mehar [EMAIL PROTECTED] wrote:
Hai Amila
I cannot give u my wsdl, did u try with a soap header with a single
element??
Code works fine with soap headers with multiple elements like
level1