Comments on: Using StAX with Spring WS

By: Pascal Alma

Pascal Alma — Mon, 12 Apr 2010 06:49:09 +0000

Hi, I don't have an example for the entire soap envelope. See the documentation here, which explains when you can access only the payload and when the complete message. I hope this helps.

By: Harish

Harish — Mon, 12 Apr 2010 06:30:59 +0000

Hi,

This is a wonderful post, it was very useful.

Please can you give me an example to parse the entire soap envelope using StAX? I should access the soap headers included in the soap envelope using StAX for my requirement.

I found that invokeInternal(XMLStreamReader streamreader,XMLStreamWriter streamwriter)method provides access only to payload (i.e content of the soap body) not to the entire soap envelope.

Regards,
K. Harish
harish.gtec@gmail.com

By: Using StAX Parsing with JBoss4.0.5.GA | Redstream Blog

Using StAX Parsing with JBoss4.0.5.GA | Redstream Blog — Fri, 06 Nov 2009 21:13:13 +0000

[...] StAX Parsing with JBoss4.0.5.GA 18 June 2008 Pascal Alma In my former post (here) I described how to combine Spring WS with StAX parsing the SOAP messages. I ended with generating [...]

By: Pascal Alma

Pascal Alma — Thu, 24 Jul 2008 12:26:13 +0000

You can just leave out the 11 in the wsdl:binding, but make sure you do the same in wsdl:port binding so the reffering name matches.

By: Vipin

Vipin — Thu, 24 Jul 2008 11:37:04 +0000

Hey,

This is a wonderful post yar… Thanks a lot. You saved a lot of time.

BTW i saw a small problem in port binding

why the name is HumanResourceSoap11 ? how can i remove the 11 from name?

regards,
Vipin

By: Pascal’s Blog » Using StAX Parsing with JBoss4.0.5.GA

Pascal’s Blog » Using StAX Parsing with JBoss4.0.5.GA — Wed, 18 Jun 2008 12:45:16 +0000

[...] my former post (here) I described how to combine Spring WS with StAX parsing the SOAP messages. I ended with generating [...]