[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sandesha-dev
Subject:    [jira] [Created] (AXIS2-5732) WSDL11ToAxisServiceBuilder fails to determine the MEP when wsdl bindin
From:       "Detelin Yordanov (JIRA)" <jira () apache ! org>
Date:       2015-11-03 11:43:27
Message-ID: JIRA.12909969.1446550975000.135965.1446551007685 () Atlassian ! JIRA
[Download RAW message or body]

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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic