axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aparna (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AXIS2-5941) version issue - Jdk 8 SOAP WS calls MEP RawXMLINOnlyMessageReceiver instead of AbstractInOutMessageReceiver
Date Wed, 21 Nov 2018 05:43:00 GMT
Aparna created AXIS2-5941:
-----------------------------

             Summary: version issue - Jdk 8 SOAP WS calls MEP RawXMLINOnlyMessageReceiver
instead of AbstractInOutMessageReceiver
                 Key: AXIS2-5941
                 URL: https://issues.apache.org/jira/browse/AXIS2-5941
             Project: Axis2
          Issue Type: Bug
            Reporter: Aparna


I have created a Java web server proxy using client's wsdl file (using axis2).  The service
works fine when I use JDK 6/7.  When I switch over to JDK 8 then internally it uses reflection
and tries to find out API method with void return type and OMElement as parameter which doesn't
exist in the ServiceSkeleton. 
 
I have posted the same question on StackOverFlow.  This is the link for more details - [https://stackoverflow.com/questions/53372508/version-issue-jdk-8-tomcat-8-web-service-calls-mep-rawxmlinonlymessagereceiv|https://www.google.com/url?q=https://stackoverflow.com/questions/53372508/version-issue-jdk-8-tomcat-8-web-service-calls-mep-rawxmlinonlymessagereceiv&sa=D&source=hangouts&ust=1542800419655000&usg=AFQjCNGyxOEKZUDa8A8uHxkMdDRb1-baCg]
 
For JDK8 - when I post the request xml from SoapUi, the call goes to org.apache.axis2.receivers.*RawXMLINOnlyMessageReceiver* where
it finds the method(void) name using reflection which doesn't exist in the serviceSkeleton.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message