[
https://wso2.org/jira/browse/MASHUP-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429#action_16429
]
Jonathan Marsh commented on MASHUP-777:
---------------------------------------
So, ROME doesn't actually normalize feeds into a common model, just mashes the
two APIs together. Kinda crappy, if I wanted to deal with different feed
variants I can just do that by trolling the XML. Does this mean that I can't
create (or simply read) an rss-type feed, save it, change feed.type="atom" and
resave it, and get two valid feeds in their respective formats? (Good source
of testcases here.)
How many other places in the API are properties dependent upon the feed type?
Do we have any expectation that users will be confused by small differences
between our API and the Rome one? If so, is it our problem the Rome API isn't
very nice or should we propose they fix it?
> Feed doesn't normalize content vs. description.
> -----------------------------------------------
>
> Key: MASHUP-777
> URL: https://wso2.org/jira/browse/MASHUP-777
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Reporter: Jonathan Marsh
> Assignee: Tyrell Perera
> Fix For: 1.1
>
>
> I have trouble using the Feed object to normalize the differences between
> these two URLs:
> http://sanjiva.weerawarana.org/feeds/posts/default
> http://auburnmarshes.spaces.live.com/feed.rss
> The former holds content in the "content" property, the latter holds it in
> the "description" property. Can we normalize these two so we can get the
> content despite what format the feed is in?
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
