[
http://opensource.atlassian.com/projects/roller/browse/ROL-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_13811
]
Dolan Halbrook commented on ROL-1444:
-------------------------------------
Hi Allen,
Have a look at this link:
http://xstream.codehaus.org/manual-tweaking-output.html
XStream offers quite a few options in tweaking XML output -- I'll do some work
to see how much this applies to the JSONOutputStream, since I have to do this
for another project anyways.
I just like the fact that we could essentially expose an XStream instance as a
Velocity tool and not worry about the model change too much in the future, but
I'm ok with going the straight Velocity route also, since I've used both kinds
of solutions in the past.
> Output JSON from FeedServlet
> ----------------------------
>
> Key: ROL-1444
> URL:
> http://opensource.atlassian.com/projects/roller/browse/ROL-1444
> Project: Roller
> Issue Type: Improvement
> Components: Newsfeed Syndication
> Affects Versions: 3.1.1, 3.2
> Environment: n/a
> Reporter: Dolan Halbrook
> Assignee: Roller Unassigned
>
> It would be useful to me to have a JSON view of the feeds generated from
> FeedServlet. I'd be willing to do the work to make this happen and donate it
> back, but as it is to make this happen I'd have to sublcass virtually all of
> the FeedServlet and I'm trying to avoid too much customization -- it would be
> much nicer to roll this back into Roller.
> Basically as I see it this would involve modifying the FeedServlet and
> creating several .vm files (such as weblog-entries-json.vm) for the JSON
> views. Not sure how to handle the XSLT view yet.
> Does anyone see any good reason not to do this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
