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

Andreas Veithen commented on AXIS2-5732:
----------------------------------------

What happens if you make the imports circular? I'm asking the question because

* I would say that EchoBindings.wsdl is invalid unless it imports 
EchoService.wsdl (because of the undefined port type);
* CXF actually has test WSDLs with circular imports: 
https://github.com/apache/cxf/tree/master/systests/ws-security/src/test/resources/wsdl_systest_wssec/wssec11.

(Note that by saying that I don't acknowledge that WSDLs with circular imports 
are actually allowed by the WSDL spec; that's a different question.)

> 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
>         Attachments: EchoService.aar, axis2.patch, axis2.patch, 
> stacktrace.txt, wsdl4j.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to