[
https://issues.apache.org/jira/browse/WW-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850291#action_12850291
]
Wes Wannemacher commented on WW-2815:
-------------------------------------
Lukasz,
XStream is what we use for the xml result type... However, we don't really
expose any mechanism for massaging the output that XStream generates... To get
an idea of what he's talking about, you can read a little bit here -
http://xstream.codehaus.org/alias-tutorial.html
I know that when I've used xstream for marshalling/unmarshalling in a Spring
app, I had some properties I could set to get rid of some of the superfluous
XML tags (like <list>...</list>). I would agree that we should try to make this
a bit more flexible, but I think it's fine to push it until 2.2.x. I'm leaving
this comment so that anyone who wants to work on it (since I haven't had much
time lately) will have a starting point.
-Wes
> No way to configure XStream engine
> ----------------------------------
>
> Key: WW-2815
> URL: https://issues.apache.org/jira/browse/WW-2815
> Project: Struts 2
> Issue Type: Improvement
> Affects Versions: 2.1.2
> Reporter: Hervé Bourzeix
> Fix For: 2.2.x
>
>
> XStream best feature is the way to configure the output but there is no way
> to control the engine other than extending current XSTream handler. It should
> be easier. An XStream engine is also created for each request, could it be
> optimized?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
