-
1. Re: How to migrate an existing Axis2 webservice client to us
stlecho May 29, 2008 10:44 AM (in response to stlecho)Hi,
I've been trying with the HttpRouter class and have been able to successfully call the Webservice, but ...-With HttpRouter I can not apply WS-Security :o(
-With HttpRouter I'm still obliged to use a Queue. I can not establish an HTTP connection with my service.
We are currently evaluating JBossESB and the described scenario is a key factor for our final decision. Any help and/or solution for these issues is more than welcome.
Regards, Stefan Lecho. -
2. Re: How to migrate an existing Axis2 webservice client to us
tfennelly May 29, 2008 11:04 AM (in response to stlecho)Hi Stefan.
can you give us more information please.
- Which version of the ESB are you using?
- Re invoking ESB endpoints via HTTP... have you tried using the jbr-listner? For an example of this, see the webservice-producer quickstart.
- When you said "with HttpRouter I can not apply WS-Security", what exactly do you mean? The HttpRouter only does what it says on the tin i.e. route message payloads over http. If you need to add "stuff" to the message before routing it, you'll need to perform some sort of transformation on the message beforehand. -
3. Re: How to migrate an existing Axis2 webservice client to us
stlecho May 29, 2008 11:35 AM (in response to stlecho)Hi,
-I'm using JBossESB v4.3GA.
-I've been doing some tests with a jbr-listener. When connection with SOAPUI to the URL (http://localhost:9876) configured for the listener, I get a Connection Refused. In the webservice-producer quickstart, the org.jboss.remoting.Client class is used. I hope :o) this is not the only way to connect to a jbr-listener.
-"WS-Security" is a standard that allows to sign SOAP Requests. I've been looking at the webservice_wssecurity quickstart, so this should not (yet) be a problem.
Regards, Stefan Lecho.