axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Detelin Yordanov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AXIS2-5732) WSDL11ToAxisServiceBuilder fails to determine the MEP when wsdl bindings are defined in an imported document
Date Tue, 03 Nov 2015 11:43:27 GMT
Detelin Yordanov created AXIS2-5732:
---------------------------------------

             Summary: WSDL11ToAxisServiceBuilder fails to determine the MEP when wsdl bindings
are defined in an imported document
                 Key: AXIS2-5732
                 URL: https://issues.apache.org/jira/browse/AXIS2-5732
             Project: Axis2
          Issue Type: Bug
          Components: kernel, wsdl
    Affects Versions: 1.6.3
            Reporter: Detelin Yordanov


When deploying a web service archive with 'useOriginalwsdl=true' and a wsdl which imports
the bindings from another document, the WSDL11ToAxisServiceBuilder fails with "Cannot Determine
the MEP" exception.
The issue seems to be caused by wsdl4j which does not properly populate binding's port type
operations, this is reported in wsdl4j jira:

https://sourceforge.net/p/wsdl4j/bugs/39/

Additionally, since Axis2 will do a depth-first search in imported wsdls to find the port
type, it will not use the port type in the parent wsdl, but the unpopulated/undefined port
type in the bindings' wsdl. 

I'm providing an 'EchoService.aar' that demonstrates the issue - please raise Axis2 log level
to DEBUG to see the exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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