-
Notifications
You must be signed in to change notification settings - Fork 41
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.
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
jaxws-rt 2.3.4 + Tomcat 9 gives WSSERVLET11: failed to parse runtime descriptor: java.lang.IllegalArgumentException: {0} is not instance of ServerPipeAssemblerContext #226
Comments
can you try 2.3.5-SNAPSHOT, and post the stacktrace again, please? It has improved error message, so one can see what gets passed to this method. Thanks! |
@lukasj, an instance of
|
hm, no luck. I would need either the service on which this fails together with the relevant piece of descriptor file OR more info about the environment (do you use any 3rd party jaxws-ri extension, like ie custom transport?) to be able to reproduce the problem |
Now that you have mentioned it. We have com.sun.xml.wss:xws-security:3.0 in the path. I created a minimal test project, but it did not initially include test project: metro-jax-ws-issue-226.zip |
you'll need Thanks for the project, I'll take a look at it. |
let me know if this won't work. The cause here is usage of com.sun.xml.wss:xws-security:3.0 which is way too old (among other things) and evolved into |
Thanks, it worked. But we had to downgrade |
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
should be fixed in 2.3.5-SNAPSHOT (your test passes on my end). Wrt the other issue related to saaj-impl - would it be possible to create an issue at https://github.com/eclipse-ee4j/metro-saaj/issues and attach failing sample there, please? There are probably more issues similar to what you see which I'm trying to fix for 1.5.4 (no ETA for that yet) and having more tests would really help. |
Will do. I try to enhance the demo project from here with a ws-security |
We have a few simple SOAP-Services using jaxws-rt running in a Tomcat 9. jaxws-rt is bundled within the war file of the service so the Tomcat as no extra libs. After updating from jaxws-rt 2.3.3 to 2.3.4 the application fails to start with the error as seen below. Downgrading to jaxws-rt 2.3.3 and the error is gone.
Java version: 11.0.11
Tomcat version: 9.0.46
Deployment descriptors: sun-jaxws.xml, web.xml
Stacktrace of error
The text was updated successfully, but these errors were encountered: