You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2009/09/07 16:16:12 UTC
[jira] Created: (SMXCOMP-631) Automatically convert StreamSource
into a re-readable type and allow user to force usage of streams
Automatically convert StreamSource into a re-readable type and allow user to force usage of streams
---------------------------------------------------------------------------------------------------
Key: SMXCOMP-631
URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
Project: ServiceMix Components
Issue Type: Improvement
Components: servicemix-camel
Affects Versions: servicemix-camel-2009.02
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: servicemix-camel-2009.02
For Camel 2.0, stream caching is no longer enabled by default. However, when using Camel inside ServiceMix, most of the times the data has to be in a re-readable format (content-based routing, multicasts, deadletter channel error handling, ...). In order to avoid that the users would have to enable stream caching on every Camel route inside ServiceMix, it would be better if we would convert our data into a re-readable type by default and allow the user to override that behavior by adding a flag to the uri.
An example:
{code}
from("jbi:name:my-endpoint").to...
-> would send a re-readable source type
from("jbi:name:my-endpoint?preserveStreams=true").to...
-> would preserve the incoming message's type, even if it's a Stream/StAXSource
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-631) Automatically convert StreamSource
into a re-readable type and allow user to force usage of streams
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54073#action_54073 ]
Gert Vanthienen commented on SMXCOMP-631:
-----------------------------------------
Lars,
The goal is to avoid putting the burden on the users for deciding when to convert from StreamSource to something else. A Camel route generally needs a re-readable source type and when you use it inside ServiceMix, the kind of Source type sent depends on the source component and the log level. The goal here is to convert to a re-readable type automatically as soon as the Message reaches the Camel endpoint, so users are not running into any unpleasant surprises when they turn off debug logging and they suddenly start running into problems.
The {{preserveStreams}} flag would be for the advanced user, who does understand the consequences of sending stream-based message into the Camel router and knows how to deal with those things inside Camel. It's kind of the other way around of what we're doing right now and it should avoid newbie users running into stream-handling issues.
Gert
> Automatically convert StreamSource into a re-readable type and allow user to force usage of streams
> ---------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-631
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
>
> For Camel 2.0, stream caching is no longer enabled by default. However, when using Camel inside ServiceMix, most of the times the data has to be in a re-readable format (content-based routing, multicasts, deadletter channel error handling, ...). In order to avoid that the users would have to enable stream caching on every Camel route inside ServiceMix, it would be better if we would convert our data into a re-readable type by default and allow the user to override that behavior by adding a flag to the uri.
> An example:
> {code}
> from("jbi:name:my-endpoint").to...
> -> would send a re-readable source type
> from("jbi:name:my-endpoint?preserveStreams=true").to...
> -> would preserve the incoming message's type, even if it's a Stream/StAXSource
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-631) Automatically convert StreamSource
into a re-readable type and allow user to force usage of streams
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54070#action_54070 ]
Lars Heinemann commented on SMXCOMP-631:
----------------------------------------
I think it's maybe the best to make the StreamDataSource itself re-readable by default. When browsing the forum there often problems arise regarding StreamSource and re-readability. Wdyt?
> Automatically convert StreamSource into a re-readable type and allow user to force usage of streams
> ---------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-631
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
>
> For Camel 2.0, stream caching is no longer enabled by default. However, when using Camel inside ServiceMix, most of the times the data has to be in a re-readable format (content-based routing, multicasts, deadletter channel error handling, ...). In order to avoid that the users would have to enable stream caching on every Camel route inside ServiceMix, it would be better if we would convert our data into a re-readable type by default and allow the user to override that behavior by adding a flag to the uri.
> An example:
> {code}
> from("jbi:name:my-endpoint").to...
> -> would send a re-readable source type
> from("jbi:name:my-endpoint?preserveStreams=true").to...
> -> would preserve the incoming message's type, even if it's a Stream/StAXSource
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-631) Automatically convert StreamSource
into a re-readable type and allow user to force usage of streams
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SMXCOMP-631:
------------------------------------
Fix Version/s: (was: servicemix-camel-2009.02)
servicemix-camel-2010.01
> Automatically convert StreamSource into a re-readable type and allow user to force usage of streams
> ---------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-631
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2010.01
>
>
> For Camel 2.0, stream caching is no longer enabled by default. However, when using Camel inside ServiceMix, most of the times the data has to be in a re-readable format (content-based routing, multicasts, deadletter channel error handling, ...). In order to avoid that the users would have to enable stream caching on every Camel route inside ServiceMix, it would be better if we would convert our data into a re-readable type by default and allow the user to override that behavior by adding a flag to the uri.
> An example:
> {code}
> from("jbi:name:my-endpoint").to...
> -> would send a re-readable source type
> from("jbi:name:my-endpoint?preserveStreams=true").to...
> -> would preserve the incoming message's type, even if it's a Stream/StAXSource
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-631) Automatically convert StreamSource
into a re-readable type and allow user to force usage of streams
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated SMXCOMP-631:
-----------------------------------------
Fix Version/s: (was: servicemix-camel-2010.01)
servicemix-camel-2010.02
> Automatically convert StreamSource into a re-readable type and allow user to force usage of streams
> ---------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-631
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2010.02
>
>
> For Camel 2.0, stream caching is no longer enabled by default. However, when using Camel inside ServiceMix, most of the times the data has to be in a re-readable format (content-based routing, multicasts, deadletter channel error handling, ...). In order to avoid that the users would have to enable stream caching on every Camel route inside ServiceMix, it would be better if we would convert our data into a re-readable type by default and allow the user to override that behavior by adding a flag to the uri.
> An example:
> {code}
> from("jbi:name:my-endpoint").to...
> -> would send a re-readable source type
> from("jbi:name:my-endpoint?preserveStreams=true").to...
> -> would preserve the incoming message's type, even if it's a Stream/StAXSource
> {code}
--
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: (SMXCOMP-631) Automatically convert
StreamSource into a re-readable type and allow user to force usage of
streams
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54070#action_54070 ]
Lars Heinemann edited comment on SMXCOMP-631 at 9/7/09 11:30 PM:
-----------------------------------------------------------------
I think it's maybe the best to make the StreamSource itself re-readable by default. When browsing the forum there often problems arise regarding StreamSource and re-readability. Wdyt?
was (Author: lhein):
I think it's maybe the best to make the StreamDataSource itself re-readable by default. When browsing the forum there often problems arise regarding StreamSource and re-readability. Wdyt?
> Automatically convert StreamSource into a re-readable type and allow user to force usage of streams
> ---------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-631
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
>
> For Camel 2.0, stream caching is no longer enabled by default. However, when using Camel inside ServiceMix, most of the times the data has to be in a re-readable format (content-based routing, multicasts, deadletter channel error handling, ...). In order to avoid that the users would have to enable stream caching on every Camel route inside ServiceMix, it would be better if we would convert our data into a re-readable type by default and allow the user to override that behavior by adding a flag to the uri.
> An example:
> {code}
> from("jbi:name:my-endpoint").to...
> -> would send a re-readable source type
> from("jbi:name:my-endpoint?preserveStreams=true").to...
> -> would preserve the incoming message's type, even if it's a Stream/StAXSource
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.