As we've implemented a custom transport (TransportTubeFactory), has anyony made progress on this?
There's JBossWSContainer inner class in RuntimeModelDeploymentAspect in Metro stack integration layer.
Its content is like this.
You should provide particular if statement to include your SPI extensions.
(after you'll make it work, you can post patch to JBossWS and we'll include it to our integration layer.)
However this approach won't work for transport layer.
Do you have just server transport implementation or client transport implementation or both?
thanks for your reply.
We have a custom transport implementation just on the client side, when JBoss calls a backend system.
Then you should face no problems IMHO.
You just need to put your classes on the classpath
and enable your implementation how is it specified
in JAX-WS RI documentation.
Thank you, Richard,
this pointed me in the right direction:
My TubelineAssemblerFactory was not used because my jar was after jbossws-metro-wsit-rt.jar in the classpath order. This jar also defines a custom TubelineAssemblerFactory and Metro silently uses the first one.
I did not patch the RuntimeModelDeploymentAspect, since it just returns null, causing Metro to search itself. I deleted the META-INF/services entry in the jbossws-metro-wsit-rt.jar and adapted my custom TubelineAssemblerFactory to imitate the WSIT-one
Now I crash into https://jira.jboss.org/jira/browse/JBWS-2301, https://jaxb.dev.java.net/issues/show_bug.cgi?id=564
Thank you again, Jan