You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Barry Kaplan (JIRA)" <ji...@apache.org> on 2009/11/24 00:27:52 UTC
[jira] Updated: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barry Kaplan updated CAMEL-2207:
--------------------------------
Attachment: Improve_types_in_RichExchanges.patch
This patch is against the 2.0, but after the 2.8 patch I submitted and was applied to trunk. Right now I can't get trunk to compile. But the changes are trivial.
> RichExchange should be using AnyRef (not Any)
> ---------------------------------------------
>
> Key: CAMEL-2207
> URL: https://issues.apache.org/activemq/browse/CAMEL-2207
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-scala
> Affects Versions: 2.0.0
> Reporter: Barry Kaplan
> Attachments: Improve_types_in_RichExchanges.patch
>
>
> RichExchange declares most of its methods using Any. But the underlying java methods declare the corresponding arguments with Object.
> For most use cases this won't matter, but statements like the following do not compile:
> if (m.erasure.isAssignableFrom(exchange.in.getClass)) { ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.