how can I get service name on the server side - SOAP over JMS
Hi! I use Axis with JMS as transport protocol. The message javax.jms.Message, which is sent over JMS, carries (in my case) just SOAP message (TextMessage). But SOAP message doesn't contain the name of the service. In my case JMS doesn't carry MessageContext, which contains the soap message, and into which I can put the service name. 1) How can I get service name on the server side? At the moment I'm setting up the sevice name with msgContext.setTargetService(Calculator) on the server side but it is fault!!! 2) Where is any documentation of configuration of axis (wsdd, how to configure Chains, ...)? Thanks, -Rehor.
Antwort: SOAP over JMS - AXIS
Hi RehorI'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.CheersOli**Oliver WulffZrich Versicherungs-GesellschaftIE4, CoC MiddlewarePostfach, 8085 ZrichTelefon: +41- 1 628 14 28Fax: +41 - 1 623 14 28E-Mail: mailto:[EMAIL PROTECTED]Rehor Vykoupil [EMAIL PROTECTED]24.05.2002 17:35 ZE2Bitte 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 manypeople have worked on it till now but I haven't found a clear and easydescription. I would like to ask whether anybody can provide me anydescription of these steps or at least what I should set up on the serverside so that the messageContext is passed and invoked successfully. I meanhow can I change the AxisServlet to MDBean with the same functionality (onthe client side I changed HTTPSender to JMSSender so JMS carries just a SOAPmessage). At the moment my problem isorg.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 PMSubject: SOAPContext I am trying to pull information out of a SOAPContext and have lookedthrough the archives but can't find any threads that address the followingstatement from the 2.2 docs: The RPCJavaProvider (the provider that runs all RPC style services) nowhas the following behavior: when searching for the method in the target classto 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 detailsof 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 methodsignature, I get an error: java.lang.NoSuchMethodException: -- no signature match Thanks Dan
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 WulffZürich Versicherungs-GesellschaftIE4, CoC MiddlewarePostfach, 8085 ZürichTelefon: +41- 1 628 14 28Fax: +41 - 1 623 14 28E-Mail: mailto:[EMAIL PROTECTED] "Rehor Vykoupil" [EMAIL PROTECTED]24.05.2002 17:35 ZE2Bitte antworten an soap-userAn: [EMAIL PROTECTED]Kopie: Blindkopie: Thema: SOAP over JMS - AXIS Hi,I am implementing the SOAP over JMS with the help of AXIS. I guess manypeople have worked on it till now but I haven't found a clear and easydescription. I would like to ask whether anybody can provide me anydescription of these steps or at least what I should set up on the serverside so that the messageContext is passed and invoked successfully. I meanhow can I change the AxisServlet to MDBean with the same functionality (onthe client side I changed HTTPSender to JMSSender so JMS carries just a SOAPmessage). 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 PMSubject: SOAPContext I am trying to pull information out of a SOAPContext and have lookedthrough the archives but can't find any threads that address the followingstatement from the 2.2 docs: "The RPCJavaProvider (the provider that runs all RPC style services) nowhas the following behavior: when searching for the method in the target classto 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 detailsof 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 methodsignature, I get an error: java.lang.NoSuchMethodException: -- no signature match Thanks Dan
Antwort: Re: Antwort: SOAP over JMS - AXIS
Hi RehorNo, 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.RegardsOliver**Oliver WulffZrich Versicherungs-GesellschaftIE4, CoC MiddlewarePostfach, 8085 ZrichTelefon: +41- 1 628 14 28Fax: +41 - 1 623 14 28E-Mail: mailto:[EMAIL PROTECTED]Rehor Vykoupil [EMAIL PROTECTED]28.05.2002 10:22 ZE2Bitte 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 AMSubject: Antwort: SOAP over JMS - AXISHi RehorI'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.CheersOli**Oliver WulffZrich Versicherungs-GesellschaftIE4, CoC MiddlewarePostfach, 8085 ZrichTelefon: +41- 1 628 14 28Fax: +41 - 1 623 14 28E-Mail: mailto:[EMAIL PROTECTED]Rehor Vykoupil [EMAIL PROTECTED]24.05.2002 17:35 ZE2Bitte antworten an soap-userAn: [EMAIL PROTECTED]Kopie: Blindkopie: Thema: SOAP over JMS - AXISHi,I am implementing the SOAP over JMS with the help of AXIS. I guess manypeople have worked on it till now but I haven't found a clear and easydescription. I would like to ask whether anybody can provide me anydescription of these steps or at least what I should set up on the serverside so that the messageContext is passed and invoked successfully. I meanhow can I change the AxisServlet to MDBean with the same functionality (onthe client side I changed HTTPSender to JMSSender so JMS carries just a SOAPmessage). At the moment my problem isorg.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 PMSubject: SOAPContext I am trying to pull information out of a SOAPContext and have lookedthrough the archives but can't find any threads that address the followingstatement from the 2.2 docs: The RPCJavaProvider (the provider that runs all RPC style services) nowhas the following behavior: when searching for the method in the target classto 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 detailsof 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 methodsignature, I get an error: java.lang.NoSuchMethodException: -- no signature match Thanks Dan
SOAP over JMS
Hi, I put some proof of concept together for sending SOAP over JMS. It's not nice, but it implements a simple JMS SOAP transport and bridge to the SOAP http server on the service side. It's similar to the Apache e-mail implementation. As said above, it's just a proof of concept, little comments and bad code. Though, I thought maybe someone is interested anyway. Put the source code into appropriate directories (see packages) in SOAP source distribution, and compile. HariNam JMSConstants.java JMSTestClient.java JMSUtil.java SOAPJMSConnection.java JMS2HTTPBridge.java
SOAP over JMS
Hello, I'm currently running a distributed app with JMS and would like to send SOAP messages across the JMS to be picked up a client and decoded as if the SOAP message was sent with a client/server architecture. This allows me to use SOAP readers in other languages such as MS SOAP for clients listening to the JMS written in the COM world. Essential the analogy is replacing the http part of SOAP with a JMS transport. I'm thinking of entering SOAP message just as java strings (or in the native string in whatever language is received by my java-language x bridge). The question is - has anyone tried shipping across a SOAP message and picking it up with a setter method on an underlying string in an Apache SOAP java class? Cheers, Neil Benn Automation Informatics Scientist Cambridge Antibody Technology
