[
http://opensource.atlassian.com/projects/roller/browse/ROL-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_13810
]
Allen Gilliland commented on ROL-1444:
--------------------------------------
Using a JSON library sounds interesting and would definitely cut into the work
load a bit, but my fear would be that the libraries don't give you enough
control over the output format and if they do something wrong you SOL. Looking
at the Xstream stuff it doesn't look like you get to make many choices, you
basically just say turn object WeblogEntry into JSON and hope it comes out
correctly, so that would make me a little nervous.
My preference would probably be to just use a velocity template so that we can
control the format ourselves, make sure only the appropriate data is included,
and also make sure that when things change from version to version that they
remain backwards compatible.
If you are willing to do that part then I can do the rest. So if can put
together some velocity templates which would be able to accept an entry or
collection of entries and comment or collection of comments and output them in
json format then that should give me enough to get started.
> 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
