You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Rich Newcomb (Assigned) (JIRA)" <ji...@apache.org> on 2011/10/04 01:53:33 UTC
[jira] [Assigned] (CAMEL-4480) RuntimeCamelException "Ambiguous
Parameter Mapping" must not be thrown, if there are parameters of the same
type but with different QNames in ServiceInterfaceStrategy
[ https://issues.apache.org/jira/browse/CAMEL-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Newcomb reassigned CAMEL-4480:
-----------------------------------
Assignee: Rich Newcomb
> 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: Rich Newcomb
>
> 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