camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-2207) RichExchange should be using AnyRef (not Any)
Date Fri, 31 Dec 2010 11:25:45 GMT

     [ 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.


Mime
View raw message