[
https://issues.apache.org/jira/browse/AXIS2-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610615#action_12610615
]
Thomas Poetter commented on AXIS2-3892:
---------------------------------------
When called this way:
InterActiveRequest request = new InterActiveRequest();
InterActiveResponse result = stub.GetInfo(request);
This exception is generated - this may be acceptable but failure could occur
more gracefully and with a more meaningful exception:
Exception in thread "main" java.lang.RuntimeException: Can not serialize OM
Element Envelope
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:1057)
at java.lang.String.valueOf(Unknown Source)
at java.lang.StringBuffer.append(Unknown Source)
at
org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:77)
at
org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
at org.apache.axis2.engine.Phase.invoke(Phase.java:317)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:429)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
InterActiveWebClientRampart.AccountInformationServiceStub.GetInfo(AccountInformationServiceStub.java:199)
at
InterActiveWebClientRampart.AccountInformationServiceCGClient.main(AccountInformationServiceCGClient.java:43)
Caused by: org.apache.axis2.databinding.ADBException: Property cannot be null!
at
InterActiveWebClientRampart.AccountInformationServiceStub$InterActiveRequest.serialize(AccountInformationServiceStub.java:37935)
at
InterActiveWebClientRampart.AccountInformationServiceStub$InterActiveRequest.serialize(AccountInformationServiceStub.java:37920)
at
InterActiveWebClientRampart.AccountInformationServiceStub$InterActiveRequest$1.serialize(AccountInformationServiceStub.java:37905)
at
org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:93)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:629)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:905)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:889)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:213)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:889)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:375)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:1051)
... 12 more
> WebServiceStub crashes with NullPointerException when web service function is
> called with null as argument
> ----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3892
> URL: https://issues.apache.org/jira/browse/AXIS2-3892
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.4
> Environment: WinXP for AXIS client + server, Rampart 1.4
> Reporter: Thomas Poetter
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Call:
> InterActiveResponse result = stub.GetInfo(null);
> Crash in:
> public InterActiveResponse GetInfo(InterActiveRequest interActiveRequest0)
> env =
> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
> interActiveRequest0, // <-- value of interActiveRequest0: null =>
> causes NullPointerException
> optimizeContent(new
> javax.xml.namespace.QName("https://xxx/AccountInformation";, "GetInfo")));
> I know that one fix is to prevent the client to call the service with null as
> argument. However, I feel the client shouldn't crash in this case but return
> null without crashing or throw an IllegalArgumentException or a similar -
> less fatal and more meaningful exception than NullPointerException.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
