axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5732) WSDL11ToAxisServiceBuilder fails to determine the MEP when wsdl bindings are defined in an imported document
Date Sun, 14 Feb 2016 18:59:18 GMT

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

Hudson commented on AXIS2-5732:
-------------------------------

SUCCESS: Integrated in axis2-1.7 #14 (See [https://builds.apache.org/job/axis2-1.7/14/])
AXIS2-5732: Merge r1730335 to the 1.7 branch. (veithen: rev 1730359)
* axis2
* axis2/modules/kernel/src/org/apache/axis2/description/WSDL11ToAxisServiceBuilder.java
* axis2/modules/kernel/test-resources/wsdl/imports
* axis2/modules/kernel/test/org/apache/axis2/description/WSDL11ToAxisServiceBuilderTest.java


> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message