In my former post (here) I described how to combine Spring WS with StAX parsing the SOAP messages. I ended with generating the WSDL as a test and said you could use Soap UI for testing the web service.
Well, I did. And I was running into the following error when I had deployed my web service at JBoss4.0.5.GA:

PLAIN TEXT
XML:
  1. <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  2.    <env:Header/>
  3.    <env:Body>
  4.       <env:Fault>
  5.          <faultcode>env:Server</faultcode>
  6.          <faultstring>Operation only supported for javax.xml.soap.Node, this is a [#comment: Test comment]</faultstring>
  7.       </env:Fault>
  8.    </env:Body>
  9. </env:Envelope>


I fixed the issue by adding the following dependencies to the project's pom.xml:

PLAIN TEXT
XML:
  1. <dependency>
  2.     <groupId>com.sun.xml.messaging.saaj</groupId>
  3.     <artifactId>saaj-impl</artifactId>
  4.     <version>1.3</version>
  5. </dependency>
  6. <dependency>
  7.     <groupId>javax.activation</groupId>
  8.     <artifactId>activation</artifactId>
  9.     <version>1.1</version>
  10.     <scope>provided</scope>
  11. </dependency>

If I don't add this dependencies, apparently Spring WS is using the JBossWS libraries as default, and these libraries can't handle the StAX parsing/writing abilities of Spring WS.
So, after adding the necessary dependencies and redeploying the web service I got the expected response:

PLAIN TEXT
XML:
  1. <soap-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  2.    <soap-ENV:Header/>
  3.    <soap-ENV:Body>
  4.       <hr:HolidayResponse xmlns:hr="http://www.pascalalma.net/hr/schemas">
  5.          <!--Test comment-->
  6.          <hr:Status>APPROVED</hr:Status>
  7.       </hr:HolidayResponse>
  8.    </soap-ENV:Body>
  9. </soap-ENV:Envelope>

I don't know about other J(2)EE Servers but for this JBoss version you need these dependencies to get it working.