You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Henryk Konsek (JIRA)" <ji...@apache.org> on 2010/09/24 10:48:40 UTC
[jira] Created: (CAMEL-3153) Omit fields configuration patch
Omit fields configuration patch
-------------------------------
Key: CAMEL-3153
URL: https://issues.apache.org/activemq/browse/CAMEL-3153
Project: Apache Camel
Issue Type: Improvement
Reporter: Henryk Konsek
Priority: Trivial
Attachments: xstream_omit_fields.patch
XStream allows to ignore selected fields for particular classes
(kind of "transient" fields). This feature is descibed here - Tweaking
XStream output (http://xstream.codehaus.org/manual-tweaking-output.html).
I needed to use that functionality in the Camel XStream data
transformation. AbstractXStreamWrapper provides support for aliases
and implicit collections but doesn't for XStream#omitField.
At this moment this problem can be handled with custom XStream Spring
FactoryBean and AbstractXStreamWrapper#setXStream method (just like I
did). However this solution is quite verbose. I think that if
AbstractXStreamWrapper supports both aliases and implicit collections
configuration, it should also supports fields omitting.
I've created patch for AbstractXStreamWrapper and unit test for it.
Maybe somebody could submit it to the codebase?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-3153) Omit fields configuration patch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-3153:
----------------------------------
Assignee: Claus Ibsen
> Omit fields configuration patch
> -------------------------------
>
> Key: CAMEL-3153
> URL: https://issues.apache.org/activemq/browse/CAMEL-3153
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Henryk Konsek
> Assignee: Claus Ibsen
> Priority: Trivial
> Attachments: xstream_omit_fields.patch
>
>
> XStream allows to ignore selected fields for particular classes
> (kind of "transient" fields). This feature is descibed here - Tweaking
> XStream output (http://xstream.codehaus.org/manual-tweaking-output.html).
> I needed to use that functionality in the Camel XStream data
> transformation. AbstractXStreamWrapper provides support for aliases
> and implicit collections but doesn't for XStream#omitField.
> At this moment this problem can be handled with custom XStream Spring
> FactoryBean and AbstractXStreamWrapper#setXStream method (just like I
> did). However this solution is quite verbose. I think that if
> AbstractXStreamWrapper supports both aliases and implicit collections
> configuration, it should also supports fields omitting.
> I've created patch for AbstractXStreamWrapper and unit test for it.
> Maybe somebody could submit it to the codebase?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3153) Omit fields configuration patch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3153:
-------------------------------
Affects Version/s: 2.4.0
Component/s: camel-xstream
> Omit fields configuration patch
> -------------------------------
>
> Key: CAMEL-3153
> URL: https://issues.apache.org/activemq/browse/CAMEL-3153
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-xstream
> Affects Versions: 2.4.0
> Reporter: Henryk Konsek
> Assignee: Claus Ibsen
> Priority: Trivial
> Fix For: 2.5.0
>
> Attachments: xstream_omit_fields.patch
>
>
> XStream allows to ignore selected fields for particular classes
> (kind of "transient" fields). This feature is descibed here - Tweaking
> XStream output (http://xstream.codehaus.org/manual-tweaking-output.html).
> I needed to use that functionality in the Camel XStream data
> transformation. AbstractXStreamWrapper provides support for aliases
> and implicit collections but doesn't for XStream#omitField.
> At this moment this problem can be handled with custom XStream Spring
> FactoryBean and AbstractXStreamWrapper#setXStream method (just like I
> did). However this solution is quite verbose. I think that if
> AbstractXStreamWrapper supports both aliases and implicit collections
> configuration, it should also supports fields omitting.
> I've created patch for AbstractXStreamWrapper and unit test for it.
> Maybe somebody could submit it to the codebase?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-3153) Omit fields configuration patch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-3153.
--------------------------------
Fix Version/s: 2.5.0
Resolution: Fixed
trunk: 1000776.
Thanks for the patch. I had to do a bit extra work to expose it in Spring XML as well.
> Omit fields configuration patch
> -------------------------------
>
> Key: CAMEL-3153
> URL: https://issues.apache.org/activemq/browse/CAMEL-3153
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-xstream
> Affects Versions: 2.4.0
> Reporter: Henryk Konsek
> Assignee: Claus Ibsen
> Priority: Trivial
> Fix For: 2.5.0
>
> Attachments: xstream_omit_fields.patch
>
>
> XStream allows to ignore selected fields for particular classes
> (kind of "transient" fields). This feature is descibed here - Tweaking
> XStream output (http://xstream.codehaus.org/manual-tweaking-output.html).
> I needed to use that functionality in the Camel XStream data
> transformation. AbstractXStreamWrapper provides support for aliases
> and implicit collections but doesn't for XStream#omitField.
> At this moment this problem can be handled with custom XStream Spring
> FactoryBean and AbstractXStreamWrapper#setXStream method (just like I
> did). However this solution is quite verbose. I think that if
> AbstractXStreamWrapper supports both aliases and implicit collections
> configuration, it should also supports fields omitting.
> I've created patch for AbstractXStreamWrapper and unit test for it.
> Maybe somebody could submit it to the codebase?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3153) Omit fields configuration patch
Posted by "Henryk Konsek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henryk Konsek updated CAMEL-3153:
---------------------------------
Attachment: xstream_omit_fields.patch
> Omit fields configuration patch
> -------------------------------
>
> Key: CAMEL-3153
> URL: https://issues.apache.org/activemq/browse/CAMEL-3153
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Henryk Konsek
> Priority: Trivial
> Attachments: xstream_omit_fields.patch
>
>
> XStream allows to ignore selected fields for particular classes
> (kind of "transient" fields). This feature is descibed here - Tweaking
> XStream output (http://xstream.codehaus.org/manual-tweaking-output.html).
> I needed to use that functionality in the Camel XStream data
> transformation. AbstractXStreamWrapper provides support for aliases
> and implicit collections but doesn't for XStream#omitField.
> At this moment this problem can be handled with custom XStream Spring
> FactoryBean and AbstractXStreamWrapper#setXStream method (just like I
> did). However this solution is quite verbose. I think that if
> AbstractXStreamWrapper supports both aliases and implicit collections
> configuration, it should also supports fields omitting.
> I've created patch for AbstractXStreamWrapper and unit test for it.
> Maybe somebody could submit it to the codebase?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.