SOAP Service - sample app fails in .NET about appsensor

[jtmelton]

After researching this and with much help from Juan C. Calderon (many thanks), it appears the issue is actually not specific to .NET. It appears it's a general issue with the sample app itself. It just so happens that the first client testing it is under .NET.

The issue is that I was using the default implementation of Jax-WS (metro), which does not play nicely with Spring's dependency injection. The objects necessary for the service were not being populated even though the service itself was starting properly.

There is a bridge tool (http://mvnrepository.com/artifact/org.jvnet.jax-ws-commons.spring/jaxws-spring), but it does not work well with spring 4. We have a couple of options:

• try to fork that project or contribute spring 4 support
• use another jax-ws implementation supporting spring

I think that using another project is the right choice here. I'm going to use CXF as it's widely used, and supports spring very well. It's feature set is generally overkill for this small project, but it does provide this needed functionality out of the box.

[jtmelton]

Pushed a few changes and asked Juan to re-test for me. Will update ticket when I have more info.

[jtmelton]

Juan was on vacation, and will be re-testing in the next couple days.

[jtmelton]

Made some updates for Juan to test, namely:

19b2911

b13d8ba

04150a0

[jtmelton]

After working through the tests with Juan, he agreed this issue is resolved for him, so marking as closed