Third identified problem is ESB integration with JBossWS.
Both org.jboss.soa.esb.actions.soap.SOAPProcessor
and org.jboss.soa.esb.actions.soap.WebserviceContractPublisher
replace our servlet transport layer.
To be more precise:
SOAPProcessor uses method
org.jboss.wsf.spi.invocation.RequestHandler.handleRequest
| (
| Endpoint endpoint,
| InputStream inputStream,
| OutputStream outputStream,
| InvocationContext context
| )
|
and WebserviceContractPublisher uses method
org.jboss.wsf.spi.invocation.RequestHandler.handleWSDLRequest
| (
| Endpoint endpoint,
| OutputStream output,
| InvocationContext context
| )
|
directly from ESB internals.
What about the WebserviceContractPublisher it even modifies the
JBossWS returned WSDL contract and rewrites it to use ESB for
messages exchange.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128820#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...