I read somewhere SoapAction is ignored in Axis server. I have successfully tested the message example. I was trying 01/30 nightly build. It didn't work if I try the message example with Alpha3 drop.
Venkat -----Original Message----- From: Romin Irani [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 12:11 PM To: [EMAIL PROTECTED] Subject: RE: Problem with Messaging Example I have made sure that the class is present in the WEB-INF/classes directory. Inspite of that, I get this message. I am suspecting something in the SOAPAction directive. Inspite of my attempts to set it to "" to default to the HTTP Url, it still gives the same problem. Any other clues ??? I am going through the AdminService class now and the AdminClient, to see if something is missing.... but the example doesnt seem to work as coded for me. Have u or anyone been successful with this "message" example. Many thanks, Romin. -----Original Message----- From: Venkat Dokiparthi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 11:59 AM To: '[EMAIL PROTECTED]' Subject: RE: Problem with Messaging Example Romin, Make sure you have copied the samples/message/MessageService.class to WEB-INF/classes directory. Or somehow make this class available to your web application. Deployment can succeed without this class being available to axis web application. Venkat -----Original Message----- From: Romin Irani [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 10:46 PM To: [EMAIL PROTECTED] Subject: Problem with Messaging Example Hi, I have been trying to run the Messaging example given in samples/message directory. The service (MessageService) deployed successfully, but when I try to run the testMessage client, I get the following error: Exception in thread "main" java.lang.NoSuchMethodException: Tried class:samples.message.MessageService , Methodname:echoElements at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:13 4) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo ntext.java:671) at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403) at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM LDocumentScanner. java:1204) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner. java:381) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098) at javax.xml.parsers.SAXParser.parse(SAXParser.java:393) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:378) at org.apache.axis.client.Call.invoke(Call.java:1268) at org.apache.axis.client.Call.invoke(Call.java:658) at samples.message.testMessage.doit(testMessage.java:32) at samples.message.testMessage.main(testMessage.java:49) ------------------ When I looked at the tcpmon trace, I saw the following SOAP Request being passed: POST /axis/services/MessageService HTTP/1.0 Content-Length: 355 Host: localhost Content-Type: text/xml; charset=utf-8 SOAPAction: "urn:foo/e1" <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <SOAP-ENV:Body><ns1:e1 xmlns:ns1="urn:foo">Hello</ns1:e1><ns2:e1 xmlns:ns2="urn:foo">World</ns2:e1> </SOAP-ENV:Body> </SOAP-ENV:Envelope> -------------- a) Can someone explain how it got the above SOAPAction value and why ? Do we have to setup the Call's HTTPAction property to "MessageService" to work. I tried that... but it gave the same problem. Kindly help me in this. Thanks. I am using Alpha-3 version. And I also tried with the latest nightly build, but no success. Romin.
