Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SOAP Service - sample app fails in .NET #16

Closed
jtmelton opened this issue Dec 17, 2014 · 5 comments
Closed

SOAP Service - sample app fails in .NET #16

jtmelton opened this issue Dec 17, 2014 · 5 comments
Labels
bug
Milestone
2.0

Comments

@jtmelton
Copy link
Owner

The sample app for the SOAP service was failing as someone was trying to use it: see http://lists.owasp.org/pipermail/owasp-appsensor-project/2014-November/000800.html.
@jtmelton
Copy link
Owner Author

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 added a commit that referenced this issue Dec 17, 2014
@jtmelton
Setting the soap config explicitly - document/literal/wrapped - part of
41a14cc 
solution for #16
jtmelton added a commit that referenced this issue Dec 17, 2014
@jtmelton
adding fast-failure for dependency injection failure on startup - part
1a21f03 
of fix for #16
jtmelton added a commit that referenced this issue Dec 17, 2014
@jtmelton
Handler chain needs to be present in the appropriate package on the
63cd0ca 
classpath. Depends on implementation, some expect it in the same package
as the handler itself, and some expect it in no package - part of fix
for #16
jtmelton added a commit that referenced this issue Dec 17, 2014
@jtmelton
adding dependencies for cxf and appropriate appsensor libs - part of fix
a9dfebd 
for #16
jtmelton added a commit that referenced this issue Dec 17, 2014
@jtmelton
excluding local response handler - part of fix for
261b07e 
#16
jtmelton added a commit that referenced this issue Dec 17, 2014
@jtmelton
moving from using metro default to cxf for sample app - part of fix for
d63d888 
#16
@jtmelton
Copy link
Owner Author

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

@jtmelton
Copy link
Owner Author

jtmelton commented Jan 4, 2015

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

@jtmelton jtmelton added the bug label Jan 4, 2015
@jtmelton jtmelton modified the milestones: 2.1, 2.0 Jan 4, 2015
jtmelton added a commit that referenced this issue Jan 5, 2015
@jtmelton
set the events collection to be static to ensure we're working with a
04150a0 
single collection - #16
@jtmelton
Copy link
Owner Author

jtmelton commented Jan 5, 2015

Made some updates for Juan to test, namely:

19b2911

b13d8ba

04150a0

@jtmelton
Copy link
Owner Author

jtmelton commented Jan 8, 2015

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

@jtmelton jtmelton closed this as completed Jan 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
1 participant
@jtmelton