You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/12/31 12:25:45 UTC
[jira] Resolved: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
[ https://issues.apache.org/jira/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2207.
--------------------------------
Resolution: Later
Fix Version/s: 2.6.0
We'll revisit camel-scala later.
And if someone in the Scala community step up and help work on camel-scala.
> RichExchange should be using AnyRef (not Any)
> ---------------------------------------------
>
> Key: CAMEL-2207
> URL: https://issues.apache.org/jira/browse/CAMEL-2207
> Project: Camel
> Issue Type: Improvement
> Components: camel-scala
> Affects Versions: 2.0.0
> Reporter: Barry Kaplan
> Assignee: james strachan
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: Improve_types_in_RichExchanges2.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.