|
osdir.com mailing list archive |
|
Subject: SOAP over JMS - AXIS - msg#00290List: text.xml.soap.userI 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" <dan.stone@xxxxxxxxx> To: <soap-user@xxxxxxxxxxxxxx> 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 > Thread at a glance:
Previous Message by Date: click to view message previewSet up Tomcat for SSL CommunicationI am new to Soap and newer to Soap over SSL. I am using TomCat 4.0.3 and trying to set up it for SSL communication. I generated the keys as instructed in the document "Setting up Apache Tomcat and a Simple Apache SOAP Client for SSL Communication." and update the server.xml with the following: <!-- Define an SSL HTTP/1.1 Connector on port 8443 --> <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" scheme="https" secure="true"> <Factory className="org.apache.catalina.net.SSLServerSocketFactory" keystoreFile="C:\webservice\server.keystore" keystorePass="changeit" clientAuth="true" protocol="TLS"/> </Connector> But when I go to https://localhost:8443/index.html, nothing is displayed, Why? I have been stuck here, any help would be much appreciated ! Jialing Next Message by Date: click to view message previewRE: no signature match for message serviceDoes you service has signature like: purchaseOrder(Envelope env, SOAPContext req, SOAPContext res) Yong -----Original Message----- From: Mark Vovsi [mailto:Mark_Vovsi@xxxxxxxxxxxx] Sent: Wednesday, May 22, 2002 2:11 PM To: soap-user@xxxxxxxxxxxxxx Subject: no signature match for message service Importance: High I'm new to soap and trying to set up some message services. I've had no problems with rpc type services, but with message services I'm getting a "no signature match" error. I checked my classpath and everything seems to be in place (my soap rpc examples work no problem), and I made sure that the root element in the soap envelope (purchaseOrder in my case) has a matching method name in my Java class. Here's the reply I get back from my server implementation. Thanks in advance. Mark. <?xml version='1.0' encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV ="http://schemas.xmlsoap.org/soap/envelope/" xm lns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd ="http://www.w3.org /1999/XMLSchema"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Server</faultcode> <faultstring>Exception while handling service request: OrderProcessor.purchaseOr der(org.apache.soap.Envelope,org.apache.soap.rpc.SOAPContext,org.apache.soap .rpc .SOAPContext) -- no signature match</faultstring> <faultactor>/soap/servlet/messagerouter</faultactor> <detail> <stackTrace>java.lang.NoSuchMethodException: OrderProcessor.purchaseOrder(org.ap ache.soap.Envelope,org.apache.soap.rpc.SOAPContext,org.apache.soap.rpc.SOAPC onte xt) -- no signature match at org.apache.soap.util.MethodUtils.getEntryPoint(MethodUtils.java:194) at org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:548) at org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:528) at org.apache.soap.server.MessageRouter.invoke(MessageRouter.java:54) at org.apache.soap.providers.MsgJavaProvider.invoke(MsgJavaProvider.java :125) at org.apache.soap.server.http.MessageRouterServlet.doPost(MessageRouter Servlet.java:268) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java: 2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche rValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java: 468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline .java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso r.java:1012) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja va:1107) at java.lang.Thread.run(Thread.java:479) </stackTrace> </detail> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Previous Message by Thread: click to view message previewSOAPContextI 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 Next Message by Thread: click to view message previewSet up Tomcat for SSL CommunicationI am new to Soap and newer to Soap over SSL. I am using TomCat 4.0.3 and trying to set up it for SSL communication. I generated the keys as instructed in the document "Setting up Apache Tomcat and a Simple Apache SOAP Client for SSL Communication." and update the server.xml with the following: <!-- Define an SSL HTTP/1.1 Connector on port 8443 --> <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" scheme="https" secure="true"> <Factory className="org.apache.catalina.net.SSLServerSocketFactory" keystoreFile="C:\webservice\server.keystore" keystorePass="changeit" clientAuth="true" protocol="TLS"/> </Connector> But when I go to https://localhost:8443/index.html, nothing is displayed, Why? I have been stuck here, any help would be much appreciated ! Jialing Loading Comments...
|
|
