 |
|||
Pragmatic Integrators |
|||
| 18 June |
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:
XML:
-
<env:envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
-
<env:header />
-
<env:body>
-
<env:fault>
-
<faultcode>env:Server</faultcode>
-
<faultstring>Operation only supported for javax.xml.soap.Node, this is a [#comment: Test comment]</faultstring>
-
</env:fault>
-
</env:body>
-
</env:envelope>
| 14 June |
As I have posted before we are using XFire to implement our web service. Unfortunately, we are running into some serious issues with the framework, so we decided to look after another implementation. Since XFire is no longer supported by the community (or at least at a very low profile) and 'replaced' by CXF, we decided to have a look at Spring WS. We also have used the Spring Framework throughout our application elsewhere, so this would be a logical choice. After a quick look at the framework it convinced us that this would be the framework to use for our web services. It was easy to set up and well documented.
Continue reading...
Top