-
15. Re: Web service security callbacks
Morning Heiko.
I have just been playing with the jmstransport unit test, trying to work out how JMS doesn't suffer from the issue we are seeing.
From what I can see, the reason it does not suffer from our issue is that it is not trying to achieve the same thing. The JMS integration that currently exists appears to be exposing *MDBs* as a webservice and not exposing *webservices* over JMS. It is also exposing them as JAX-RPC endpoints instead of JAX-WS ones (hence avoiding the warning) . Is my correct or do I only have part of the puzzle?
.
What we are trying to achieve (at least in this instance) is to expose co-located *webservices* through the ESB without having to make an invocation over HTTP. We don't care whether the implementation of those webservices is 181, an MDB, JSE or otherwise. We are trying to act as an independent transport mechanism for jbossws.
This topic certainly needs more discussion but I do not feel that JBW is the appropriate place. Tom Fennelly has done the majority of this work and he should also be involved in these discussions. -
16. Re: Web service security callbacks
"Kevin.Conner@jboss.com" wrote:
This topic certainly needs more discussion but I do not feel that JBW is the appropriate place. Tom Fennelly has done the majority of this work and he should also be involved in these discussions.
Good point and in which case it will definitely have to wait as Tom current tasks have higher priority, as you know.