Hi Rehor
No, I didn't because the interface for forwarding the soap request depends on the httpservlet. Because I have a JMS listener I have no httpservlet. Currently, we are looking for a solution with the company IONA which provide the product XMLBus (www.xmlbus.com). Perhaps in the future, they will also provide a JMS listener for XMLBus. I've written a simple JMS listener by myself to forward the request to XMLBus. This scenario was just a test to proof that SOAP over JMS is working.
I don't know if you can register another transport protocol in Axis or if you have to build your own runtime (JMS listener) and can reuse some classes from Axis.
Regards
Oliver
******************************************************************
Oliver Wulff
Zürich Versicherungs-Gesellschaft
IE4, CoC Middleware
Postfach, 8085 Zürich
Telefon: +41- 1 628 14 28
Fax: +41 - 1 623 14 28
E-Mail: mailto:[EMAIL PROTECTED]
"Rehor Vykoupil" <[EMAIL PROTECTED]>
28.05.2002 10:22 ZE2
Bitte antworten an soap-user
An: <[EMAIL PROTECTED]>
Kopie:
Blindkopie:
Thema: Re: Antwort: SOAP over JMS - AXIS
Hi Oli,
thanks for your info. Have you tried to register the listener, which is different to http, and to forward the message? I mean what everything should be done.
Can you provide me, please, a links or examples of the sollutions you just provided me?
Thank you,
-Rehor.
----- Original Message -----
From: Oliver Wulff
To: [EMAIL PROTECTED]
Sent: Tuesday, May 28, 2002 10:07 AM
Subject: Antwort: SOAP over JMS - AXIS
Hi Rehor
I've implemented something similar for Apache SOAP. It's working fine for the client (also synchronous) but the server side implementation looks completly different. There were dependencies to the httpservlet in upon layers (ejb, java delegation code). There should be a clean interface between the transport (http, jms) and the delegation layer (ejb, java, ...). It sounds that it's not much better solved in axis. You should have the possibility to start your own listener and delegate the soap message to the "delegation code" or axis has a pluggable architecture where you can register other listener than http and forward the soap message to the same classes.
Cheers
Oli
******************************************************************
Oliver Wulff
Zürich Versicherungs-Gesellschaft
IE4, CoC Middleware
Postfach, 8085 Zürich
Telefon: +41- 1 628 14 28
Fax: +41 - 1 623 14 28
E-Mail: mailto:[EMAIL PROTECTED]
"Rehor Vykoupil" <[EMAIL PROTECTED]>
24.05.2002 17:35 ZE2
Bitte antworten an soap-user
An: <[EMAIL PROTECTED]>
Kopie:
Blindkopie:
Thema: SOAP over JMS - AXIS
Hi,
I am implementing the SOAP over JMS with the help of AXIS. I guess many
people have worked on it till now but I haven't found a clear and easy
description. I would like to ask whether anybody can provide me any
description of these steps or at least what I should set up on the server
side so that the messageContext is passed and invoked successfully. I mean
how can I change the AxisServlet to MDBean with the same functionality (on
the client side I changed HTTPSender to JMSSender so JMS carries just a SOAP
message). At the moment my problem is
"org.apache.axis.ConfigurationException: java.lang.ClassNotFoundException:
org.apache.axis.handlers.http.URLMapper".
Thanks,
Rehor.
----- Original Message -----
From: "Dan Stone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 24, 2002 5:05 PM
Subject: SOAPContext
> I am trying to pull information out of a SOAPContext and have looked
through
> the archives but can't find any threads that address the following
statement
> from the 2.2 docs:
>
> "The RPCJavaProvider (the provider that runs all RPC style services) now
has
> the following behavior: when searching for the method in the target class
to
> call to process the service request, if a method with a matching signature
> is not found, then a second search is done. The second search looks for a
> method with an additional (first) argument of type
> org.apache.soap.rpc.SOAPContext (please see the API docs for the details
of
> that class). If found, then an instance of SOAPContext is passed to the
> service handler class. "
>
> Do I need to do anything besides specify this additional argument in my
> service method?
> Because when I introduce this SOAPContext argument to the method
signature,
> I get an error:
>
> java.lang.NoSuchMethodException: -- no signature match
>
>
> Thanks
> Dan
>
