[ 
https://issues.apache.org/jira/browse/CAMEL-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang resolved CAMEL-4480.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9.0
                   2.8.2
    
> RuntimeCamelException "Ambiguous Parameter Mapping" must not be thrown, if 
> there are parameters of the same type but with different QNames in 
> ServiceInterfaceStrategy
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4480
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4480
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-soap
>    Affects Versions: 2.8.1
>            Reporter: Oliver Jelinski
>            Assignee: Willem Jiang
>             Fix For: 2.8.2, 2.9.0
>
>         Attachments: camel-4480-trunk.patch
>
>
> In different WebMethods I have parameters of the same type, but with 
> different QNames. The following if-clause (in 
> ServiceInterfaceStrategy.analyzeServiceInterface(..)) throws an exeption in 
> these cases (thrown if NOT QNameOfMethod1 equals QNameOfMethod2), but it 
> should on the contrary throw an exception if the QNames ARE equal:
>                 if (inTypeNameToQName.containsKey(ti.getTypeName())
>                     && (!(ti.getTypeName().equals("javax.xml.ws.Holder")))
>                     && 
> (!(inTypeNameToQName.get(ti.getTypeName()).equals(ti.getElName())))) {
>                     throw new RuntimeCamelException("Ambiguous parameter 
> mapping. The type [ "
>                                                     + ti.getTypeName()
>                                                     + " ] is already mapped 
> to a QName in this context.");
>                 }
> The "NOT" must be deleted:
> ...
> && (inTypeNameToQName.get(ti.getTypeName()).equals(ti.getElName())))
> ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to