project.xml
v 1.14
src/data/rss_1.0.xml
v 1.4
src/data/rss_1.0_DC_Sy.xml
v 1.4
src/data/rss_1.0_DC_multi.xml
v 1.2
src/data/rss_2.0.xml
v 1.6
src/java/com/sun/syndication/feed/atom/Content.java
v 1.6
src/java/com/sun/syndication/feed/rss/Content.java
v 1.1
src/java/com/sun/syndication/feed/rss/Item.java
v 1.10
src/java/com/sun/syndication/feed/synd/SyndContent.java
v 1.6
src/java/com/sun/syndication/feed/synd/SyndContentImpl.java
v 1.6
src/java/com/sun/syndication/feed/synd/SyndEntryImpl.java
v 1.19
src/java/com/sun/syndication/feed/synd/impl/ConverterForAtom03.java
v 1.18
src/java/com/sun/syndication/feed/synd/impl/ConverterForRSS091Userland.java
v 1.6
src/java/com/sun/syndication/feed/synd/impl/ConverterForRSS10.java
v 1.11
src/java/com/sun/syndication/io/impl/Atom03Generator.java
v 1.11
src/java/com/sun/syndication/io/impl/Atom03Parser.java
v 1.16
src/java/com/sun/syndication/io/impl/Atom10Generator.java
v 1.8
src/java/com/sun/syndication/io/impl/Atom10Parser.java
v 1.15
src/java/com/sun/syndication/io/impl/RSS090Generator.java
v 1.9
src/java/com/sun/syndication/io/impl/RSS090Parser.java
v 1.10
src/java/com/sun/syndication/io/impl/RSS091UserlandGenerator.java
v 1.4
src/java/com/sun/syndication/io/impl/RSS091UserlandParser.java
v 1.6
src/java/com/sun/syndication/io/impl/RSS10Generator.java
v 1.9
src/java/com/sun/syndication/io/impl/RSS10Parser.java
v 1.7
src/test/com/sun/syndication/unittest/TestSyndFeedRSS10.java
v 1.5
src/test/com/sun/syndication/unittest/TestSyndFeedRSS20.java
v 1.4
*** Plan for RSS/Atom summary/content mapping I believe the consensus for summary/content mapping to/from RSS/Atom was the plan that I proposed plus suggestions from Sam Ruby. Here's the plan w/Sam's suggestions: https://rome.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1679 Basically, it boils down to this: When converting RSS to Atom, we want to map rss.item.description -> atom.entry.summary rss.item.content:encoded -> atom.entry.content When converting Atom to RSS, we want to map atom.entry.summary -> rss.item.description atom.entry.content -> rss.item.content:encoded To implement the plan, I added built-in support for the <content:encoded> part of the Content Module into ROME. I did that, but we ensure that we do not interfere with the any existing Content Module implementations. So, we parse <content:encoded>, but we'll only generate it when the Content Module is not in play. *** Summary of work done --- com/sun/syndication/feed/rss/Content.java Add a new RSS Content class to model <content:encoded> --- com/sun/syndication/feed/rss/Item.java Add new item.content property in RSS item object --- RSS10Parser.java In parseItem() method, add parsing for <content:encoded> --- RSS091UserlandParser.java In parseItem() method, add parsing for <content:encoded> --- ConverterForRSS091Userland.java Implement the conversion rules we agreed upon createRSSItem() synd.content -> rss.content synd.description -> rss.description createSyndEntry() rss.content -> synd.content rss.description -> synd.description --- ConverterForRSS091Userland.java Implement the conversion rules we agreed upon Same as above --- RSS10Generator.java In populateItem(), generate <content:encoded> if needed, but only when any Content module is not in play* --- RSS091UserlandGenerator.java In populateItem(), generate <content:encoded> if needed, but only when Content module is not in play* * If there is a generator registered to handle the Conent Module URI, then we consider it to be in play. |