[
https://issues.apache.org/jira/browse/AXIS2-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Detelin Yordanov updated AXIS2-5732:
------------------------------------
Attachment: axis2.patch
I have not been able to reproduce an issue with circular imports even without
the fix in wsdl4j. I have added a similar test case as the one you pointed to
in CXF and it is successful with the latest patch I have provided. I also added
a more complex test case where we have "service -> bindings -> port type"
import chain and this one is also handled, thanks to the fall back to binding's
portType when it cannot be found in the definition (indeed with such imports,
the port type will be null when looked up via definition.getPortType() since
this method will only search direct imports but not transitive imports).
All of this means that Axis2 could use CXF approach to look up the port type
and work even without the wsdl4j fix.
> 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, 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]
