You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2008/10/24 10:15:52 UTC
[jira] Created: (CAMEL-1025) [IDEA] could we refactor the type
conversion code so it can be reused in other scenarios outside of a camel
message exchange?
[IDEA] could we refactor the type conversion code so it can be reused in other scenarios outside of a camel message exchange?
-----------------------------------------------------------------------------------------------------------------------------
Key: CAMEL-1025
URL: https://issues.apache.org/activemq/browse/CAMEL-1025
Project: Apache Camel
Issue Type: Improvement
Reporter: James Strachan
Fix For: Future
I'd have thoughts lots of libraries would find the type conversion mechanism very useful?
No biggie but I wonder how Camel API dependent it really is - e.g. does it really need to depend on Exchange?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1025) [IDEA] could we refactor the type
conversion code so it can be reused in other scenarios outside of a camel
message exchange?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1025.
--------------------------------
Resolution: Won't Fix
Lets stick Camel to Camel
> [IDEA] could we refactor the type conversion code so it can be reused in other scenarios outside of a camel message exchange?
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1025
> URL: https://issues.apache.org/activemq/browse/CAMEL-1025
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Fix For: Future
>
>
> I'd have thoughts lots of libraries would find the type conversion mechanism very useful?
> No biggie but I wonder how Camel API dependent it really is - e.g. does it really need to depend on Exchange?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1025) [IDEA] could we refactor the type
conversion code so it can be reused in other scenarios outside of a camel
message exchange?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51877#action_51877 ]
Claus Ibsen commented on CAMEL-1025:
------------------------------------
It depends on Exchange because then it can get hold on CamelContext to get hold of the TypeConverterRegistry where we can leverage other type converters.
Depending on Exchange also allows us to read properties/headers set for eg desired charset. For instance used by the byte[] converters.
So it is somewhat dependent on this. I dont think its feasable to break this to allow the type converter to be 100% not dependent on the Camel API.
> [IDEA] could we refactor the type conversion code so it can be reused in other scenarios outside of a camel message exchange?
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1025
> URL: https://issues.apache.org/activemq/browse/CAMEL-1025
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Fix For: Future
>
>
> I'd have thoughts lots of libraries would find the type conversion mechanism very useful?
> No biggie but I wonder how Camel API dependent it really is - e.g. does it really need to depend on Exchange?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.