|
||||||||
|
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 |
||||||||
To unsubscribe from this list please visit:
Hi Kohsuke,
with this patch you have an elegant solution for this problem, but it is unfortunately not the way we got in XStream. Annotations should always trigger functionality that is configurable with the XStream facade, because not everyone wants to have a hard reference to XStream in the projects model nor do you always control the classes where you would like to add the annotation.
However, for the upcoming release I'd simply expose the test for a transient field by moving the condition from the nested code part in method visitSerializableFields into method fieldModifiersSupported. That way you can then overload this method only by a derived ReflectionConvertor implementation.
Would that be enough for now to use a stock XStream release?