axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Clegg" <>
Subject SOAP fault "Could not initialize class ..."
Date Tue, 24 Jun 2008 16:05:47 GMT
Afternoon all,

I'm trying to get some XMLBeans-based service stubs in place and I'm
hitting an odd problem which I can't find any reference to via Google.

The services deploy to the server fine, with no error messages, and I
can see them in http://localhost:8080/axis2/services/ and view the
WSDLs. Everything looks okay.

The built-in Version service works okay, but whenever I try to run one
of mine (e.g. via SoapUI), I get a response like this:

<soapenv:Envelope xmlns:soapenv="">
         <faultstring>Could not initialize class</faultstring>

(This is for a service called Test with a TestEcho operation, the
classic 'hello world' for request/response services.)

I have checked in my repository and TestEchoDocument.class is exactly
where it should be, in, having compiled with no

The Java code in looks like this:

    public TestEcho( testEcho0) {
        TestEchoResponseDocument rDoc =
        TestEchoResponse r = rDoc.addNewTestEchoResponse();
        r.setOutputText( testEcho0.getTestEcho().getInputText() );
        return rDoc;

Please let me know if I'm doing something completely wrong! I can post
the WSDL and XSD (or the relevant parts) if that would help.

Also, on a related note, if I change the TestEcho method to throw back
an exception instead, the text of the exception isn't reflected in the
soap message returned. It just says:

<soapenv:Envelope xmlns:soapenv="">

Is there a way to have Axis2 pass the exception text back to the
client? This would be quite helpful for debugging.

Thanks in advance for any suggestions, and sorry if any of these
questions have obvious answers, I'm a complete Axis newbie.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message