[ 
https://issues.apache.org/jira/browse/AXIS2-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074106#comment-17074106
 ] 

Steve Schaefer commented on AXIS2-5981:
---------------------------------------

Thanks for the suggestion Robert,

I'm unable to access the response (result) because it's out of scope when the 
exception is caught. Any other suggestions? One thing that did change after 
axis2 1.3 was it now requires a namespace when creating OMAbstractFactory 
createOMNamespace. In 1.3 we were setting the namespace to an empty string 
which I know isn't valid in 1.6.4 and above.

  OMElement result = client.sendReceive(method);
  if (result != null)
  {
    System.out.print(result.toString());
  }
 }
 catch (Exception e)
 {
  // cant access result here
  System.out.print(e.getMessage());
 }

> AXIS2 1.7.9 lower cases element name in ServiceClient object sendReceive() 
> method
> ---------------------------------------------------------------------------------
>
>                 Key: AXIS2-5981
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5981
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.7.9
>         Environment: Windows 10 Enterprise Build 10.0.18363
>            Reporter: Steve Schaefer
>            Priority: Major
>
> I've upgraded from AXIS2 1.3 to 1.7.9 and the call to my SOAP service stopped 
> working. It's returning the exception "org.apache.axis2.AxisFault: while 
> trying to invoke the method org.apache.axiom.om.OMElement.getText() of a null 
> object loaded from local variable 'runidNode'". I can see that I'm passing 
> the mixed case runID into the sendReceive() method but the SOAP service is 
> receiving it all lower case? I get the same error if I call the service from 
> Postman with all lowercase "runid" element.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to