You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (Commented) (JIRA)" <ji...@apache.org> on 2012/04/16 04:47:16 UTC
[jira] [Commented] (CAMEL-5176) CxfProducer should not always
leverage toList type converter to find out the parameters for invocation
[ https://issues.apache.org/jira/browse/CAMEL-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254489#comment-13254489 ]
Willem Jiang commented on CAMEL-5176:
-------------------------------------
We should update the code on the other camel branches, as it's a common use case these versions.
> CxfProducer should not always leverage toList type converter to find out the parameters for invocation
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5176
> URL: https://issues.apache.org/jira/browse/CAMEL-5176
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.10.0
>
>
> CAMEL-5173 removed the two type converters which could always to load the classes and it broke the itest of CxfToJmsInOutTest.
> After digging the code for a while I found the CxfProducer always looks up the parameter by turning the message body into a List. With the change of CAMEL-5173, Camel will turn the message body into a List of ActiveQueue (as the String --> List converter are wildly used).
> To fix this issue, we should let the CxfProducer pick up the parameter carefully.
--
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