Loading ...
Sorry, an error occurred while loading the content.

Re: SOAPLite webservices & Java Clien

Expand Messages
  • Kirti Bodhmage
    Thanks for the suggestion. I followed the suggestion but now axis is throwing an exception while getting the soap response. any suggestion? Exception in thread
    Message 1 of 1 , Apr 10 6:17 AM
    • 0 Attachment
      Thanks for the suggestion. I followed the suggestion but now axis is
      throwing an exception while getting the soap response.
      any suggestion?

      Exception in thread "main" AxisFault
      faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
      faultSubcode:
      faultString: org.xml.sax.SAXParseException: Comment must start with
      "<!--".
      faultActor:
      faultNode:
      faultDetail:
      {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException:
      Comment must start with "<!--".
      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
      Source)
      at javax.xml.parsers.SAXParser.parse(Unknown Source)
      at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
      at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
      at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
      at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
      at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
      at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
      at org.apache.axis.client.Call.invoke(Call.java:2767)
      at org.apache.axis.client.Call.invoke(Call.java:2443)
      at org.apache.axis.client.Call.invoke(Call.java:2366)
      at org.apache.axis.client.Call.invoke(Call.java:1812)
      at Demo.SoapDemoBindingStub.hi(SoapDemoBindingStub.java:99)
      at Demo.MyTest.main(MyTest.java:17)

      {http://xml.apache.org/axis/}hostname:ANDREW

      org.xml.sax.SAXParseException: Comment must start with "<!--".
      at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
      at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
      at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
      at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
      at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
      at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
      at org.apache.axis.client.Call.invoke(Call.java:2767)
      at org.apache.axis.client.Call.invoke(Call.java:2443)
      at org.apache.axis.client.Call.invoke(Call.java:2366)
      at org.apache.axis.client.Call.invoke(Call.java:1812)
      at Demo.SoapDemoBindingStub.hi(SoapDemoBindingStub.java:99)
      at Demo.MyTest.main(MyTest.java:17)
      Caused by: org.xml.sax.SAXParseException: Comment must start with "<!--".
      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
      Source)
      at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
      Source)
      at javax.xml.parsers.SAXParser.parse(Unknown Source)
      at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
      at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
      ... 10 more



      On 05/04/07, pfconrey <pfconrey@...> wrote:
      > --- In soaplite@yahoogroups.com, "mkirti" <kbodhmage@...> wrote:
      > Kirti,
      >
      > I'm doing quite a bit of this right now. Here are the steps:
      >
      > 1. Write a WSDL file that matches the output of your service. This
      > may take a little research, but it's not terribly hard to do.
      >
      > 2. Using Apache Axis, generate Java client objects with the WSDL2Java
      > tool. This will generate a proxy class for each object you have
      > defined in your WSDL, as well as a set of classes for connecting to
      > the service.
      >
      > 3. Using the PortType object generated by WSDL2Java (assuming your
      > service is named "Service", the class would be called
      > ServicePortType), call the appropriate method.
      >
      > I've over simplified this a bit, but it should get you going in the
      > right direction.
      >
      > Also, I would look at getting one of the free utilities for testing
      > WSDLs and Web Services, such as .NET Web Service Studio. I think
      > there's a Java base tool that does the same thing, but I'm not sure
      > what it's called.
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.