[
https://issues.apache.org/jira/browse/YOKO-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darren Middleman resolved YOKO-351.
-----------------------------------
Resolution: Fixed
Fix Version/s: v1.0.0
Revision 530856 contains complete fix and test cases.
> Operations with identical names but in different scopes result in duplicate
> schema elements being generated in WSDL
> -------------------------------------------------------------------------------------------------------------------
>
> Key: YOKO-351
> URL: https://issues.apache.org/jira/browse/YOKO-351
> Project: Yoko - CORBA Server
> Issue Type: Bug
> Components: Idl2Wsdl
> Affects Versions: v1.0-incubating-M2
> Reporter: Darren Middleman
> Assigned To: Darren Middleman
> Fix For: v1.0.0
>
>
> Using an IDL such as:
> module A {
> interface AInterface {
> void testOp();
> };
> };
> module B {
> interface BInterface {
> void testOp();
> };
> };
> results in a WSDL with duplicate elements called testOp. This causes issues
> when the elements are referenced later in the WSDL.
> A fix would be to prefix any element names which already exist in the WSDL
> with the scoping name so that the second testOp in the example above would be
> changed to B_BInterface_testOp. The generated CORBA binding information in
> the WSDL would still maintain the original operation name as this is needed
> when making the CORBA invocation.
> e.g.
> <wsdl:binding name="B.BInterfaceCORBABinding" type="tns:B.BInterface">
> <corba:binding repositoryID="IDL:B/BInterface:1.0" />
> <wsdl:operation name="B_BInterface_testOp">
> <corba:operation name="testOp"/>
> <wsdl:input name="B_BInterface_testOpRequest">
> </wsdl:input>
> <wsdl:output name="B_BInterface_testOpResponse">
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
