You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "liugang (JIRA)" <ji...@apache.org> on 2012/10/26 11:15:12 UTC
[jira] [Created] (CAMEL-5746) WireTap will always copy the origin
Message
liugang created CAMEL-5746:
------------------------------
Summary: WireTap will always copy the origin Message
Key: CAMEL-5746
URL: https://issues.apache.org/jira/browse/CAMEL-5746
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.10.2
Environment: Camel 2.10.2
Reporter: liugang
Priority: Minor
I found the wiretap will always copy the original exchange message after deprecated those methods like -wireTap(String uri, boolean copy, Expression body)- and -wireTap(String uri, boolean copy, Processor processor)- .
Checked the source code of *org.apache.camel.model.WireTapDefinition<Type>*, the *isCopy()* and *copy()* method are:
{code}
public WireTapDefinition<Type> copy() {
setCopy(true);
return this;
}
public boolean isCopy() {
// should default to true if not configured
return copy != null ? copy : true;
}
{code}
So, no matter, we use '.wireTap("XX")' or '.wireTap("XX").copy()' , it will always copy the original exchange message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5746) WireTap will always copy the origin
Message
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-5746.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.11.0
2.10.3
2.9.5
Applied the patch into trunk, camel-2.10.x and camel-2.9.x branches.
> WireTap will always copy the origin Message
> -------------------------------------------
>
> Key: CAMEL-5746
> URL: https://issues.apache.org/jira/browse/CAMEL-5746
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: Camel 2.10.2
> Reporter: liugang
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.9.5, 2.10.3, 2.11.0
>
>
> I found the wiretap will always copy the original exchange message after deprecated those methods like -wireTap(String uri, boolean copy, Expression body)- and -wireTap(String uri, boolean copy, Processor processor)- .
> Checked the source code of *org.apache.camel.model.WireTapDefinition<Type>*, the *isCopy()* and *copy()* method are:
> {code}
> public WireTapDefinition<Type> copy() {
> setCopy(true);
> return this;
> }
> public boolean isCopy() {
> // should default to true if not configured
> return copy != null ? copy : true;
> }
> {code}
> So, no matter, we use '.wireTap("XX")' or '.wireTap("XX").copy()' , it will always copy the original exchange message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-5746) WireTap will always copy the origin
Message
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-5746:
-----------------------------------
Assignee: Willem Jiang
> WireTap will always copy the origin Message
> -------------------------------------------
>
> Key: CAMEL-5746
> URL: https://issues.apache.org/jira/browse/CAMEL-5746
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: Camel 2.10.2
> Reporter: liugang
> Assignee: Willem Jiang
> Priority: Minor
>
> I found the wiretap will always copy the original exchange message after deprecated those methods like -wireTap(String uri, boolean copy, Expression body)- and -wireTap(String uri, boolean copy, Processor processor)- .
> Checked the source code of *org.apache.camel.model.WireTapDefinition<Type>*, the *isCopy()* and *copy()* method are:
> {code}
> public WireTapDefinition<Type> copy() {
> setCopy(true);
> return this;
> }
> public boolean isCopy() {
> // should default to true if not configured
> return copy != null ? copy : true;
> }
> {code}
> So, no matter, we use '.wireTap("XX")' or '.wireTap("XX").copy()' , it will always copy the original exchange message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5746) WireTap will always copy the origin
Message
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484878#comment-13484878 ]
Willem Jiang commented on CAMEL-5746:
-------------------------------------
We could add a fluent to set if camel copy the origin Message.
> WireTap will always copy the origin Message
> -------------------------------------------
>
> Key: CAMEL-5746
> URL: https://issues.apache.org/jira/browse/CAMEL-5746
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: Camel 2.10.2
> Reporter: liugang
> Priority: Minor
>
> I found the wiretap will always copy the original exchange message after deprecated those methods like -wireTap(String uri, boolean copy, Expression body)- and -wireTap(String uri, boolean copy, Processor processor)- .
> Checked the source code of *org.apache.camel.model.WireTapDefinition<Type>*, the *isCopy()* and *copy()* method are:
> {code}
> public WireTapDefinition<Type> copy() {
> setCopy(true);
> return this;
> }
> public boolean isCopy() {
> // should default to true if not configured
> return copy != null ? copy : true;
> }
> {code}
> So, no matter, we use '.wireTap("XX")' or '.wireTap("XX").copy()' , it will always copy the original exchange message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira