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/20 23:17:52 UTC
[jira] Created: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
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
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.
[jira] Issue Comment Edited: (CAMEL-2207) RichExchange should be
using AnyRef (not Any)
Posted by "Barry Kaplan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56036#action_56036 ]
Barry Kaplan edited comment on CAMEL-2207 at 11/23/09 3:29 PM:
---------------------------------------------------------------
patch update
was (Author: memelet):
update
> 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_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.
[jira] Updated: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Barry Kaplan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barry Kaplan updated CAMEL-2207:
--------------------------------
Attachment: (was: Improve_types_in_RichExchanges.patch)
> 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_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.
[jira] Assigned: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-2207:
----------------------------------
Assignee: James Strachan
> 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
> Assignee: James Strachan
> 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.
[jira] Commented: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Barry Kaplan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56039#action_56039 ]
Barry Kaplan commented on CAMEL-2207:
-------------------------------------
This patch is bogus. I broke lots of tests. (I thought the tests passed but they did not run.)
> 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_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.
[jira] Updated: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Barry Kaplan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55662#action_55662 ]
Claus Ibsen commented on CAMEL-2207:
------------------------------------
Barry feel free to contribute patches on the camel-scala
> 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
>
> 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.
[jira] Updated: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-2207:
-------------------------------
Issue Type: Improvement (was: Bug)
Priority: Minor (was: Major)
> RichExchange should be using AnyRef (not Any)
> ---------------------------------------------
>
> Key: CAMEL-2207
> URL: https://issues.apache.org/activemq/browse/CAMEL-2207
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-scala
> Affects Versions: 2.0.0
> Reporter: Barry Kaplan
> Assignee: James Strachan
> Priority: Minor
> 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.
[jira] Updated: (CAMEL-2207) RichExchange should be using AnyRef
(not Any)
Posted by "Barry Kaplan (JIRA)" <ji...@apache.org>.
[ 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_RichExchanges2.patch
update
> 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_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.