Line 994, 1009, etc are in error:
<soap:fault name=""
Don't know what impact this has but you need to vet your WSDL very carefully (I use both XMLSpy & the WS-I checks from within Eclipse). Axis seems to accept incorrect WSDL & gernerate dodgey code as a result.
On 7/10/06, Gmail <[EMAIL PROTECTED]> wrote:
Hi. I am new to axis.
# apache axis 1.4 - newest version!
# no depends on java version - get the same error on sun jdk 1.4.1 an sun jdk 1.5.0_06
But I think that following is a axis bug!!
If not, please help me!!
I use client Bindings and server Implementation generated with wsdl2java.
Using generated TestCase i send soap request to server and didn't get response except AxisFault:
I try to retrieve na Array of objects ( Subscriber[] - java code in attachement - if this help you ) in response
Moreover the SoapMonitor show valid soap request but didn't show response (status - Active)
//-------------------------------------------------------------------------------------------------------------
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NullPointerException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:phoenix.ustronie.pw.edu.pl
java.lang.NullPointerException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java :129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1528)
at org.apache.crimson.parser.Parser2.content (Parser2.java:1779)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
at org.apache.crimson.parser.Parser2.maybeElement (Parser2.java:1507)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at org.apache.crimson.parser.XMLReaderImpl.parse (XMLReaderImpl.java:442)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
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 usn.oam.web.soap.prov.wsdl.ProvisioningManagerBindingStub.retrieveSubscriber(ProvisioningManagerBindingStub.java :2083)
at usn.oam.web.soap.prov.wsdl.HSNProvisioningServiceTestCase.test21ProvisioningManagerPortRetrieveSubscriber(HSNProvisioningServiceTestCase.java:684)
at usn.oam.web.soap.prov.wsdl.HSNClientSideTester.executeCommand (HSNClientSideTester.java:97)
at usn.oam.web.soap.prov.wsdl.HSNClientSideTester.fileCommandWrapper(HSNClientSideTester.java:157)
at usn.oam.web.soap.prov.wsdl.HSNClientSideTester.main(HSNClientSideTester.java :188)
//------------------------------------------------------------------------------------------------------------------------
Is it a client side bug or server side??
I think that is server error but why??
Is there any problem with arrays of objects??
best regards
Borowski Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
