I went ahead and starting working on this.

I have a question regarding the mapping of links in a SyndFeed.  Would 
these map to RssItems?  Currently I'm mapping SyndEnty's to RssItems but 
wasn't sure if I should do the same for links.

Thanks for the clarification.  I'll post what I've mapped on the 
syndication side to the RSS side as there are other items I'm not 100% 
sure about when I'm done just to make sure that it's correct.

-- Jesse




From:
Shiva Kumar H R <[email protected]>
To:
[email protected]
Date:
03/18/2010 08:18 PM
Subject:
Re: Map RSS to Syndication Object Model



Many thanks Jesse. I will look further into this.

Thanks,
Shiva Kumar H R

On Thu, Mar 18, 2010 at 8:02 PM, Jesse A Ramos <[email protected]> wrote:

> Hi Shiva,
>
> I took a look at this yesterday to see if I could figure out what needed
> to be done.  This is what I found.
>
> In org.apache.wink.common.model.atom the ATOM Object model classes have
> constructors that accept the Objects from
> org.apache.wink.common.model.synd (ex: the constructor 
AtomFeed(SyndFeed))
> which allow the syndication Objects to be converted to ATOM Objects.
> Similarly, there are adapter classes under
> org.apache.wink.server.internal.entity.html that allow a conversion to
> html.
>
> Additionally, there are provides (AtomFeedSyndFeedProvider,
> AtomEntrySyndEntryProvider, HtmlSyndFeedProvider, and
> HtmlSyndEntryProvider) which allow syndication Objects to be serialized 
to
> those other formats and which make use of the adapters.
>
> I believe that the JIRA was created to add similar support to the RSS
> Object model.
>
> -- Jesse
>
> >I need some help in resolving JIRA
> >https://issues.apache.org/jira/browse/WINK-149 "Map RSS to Syndication
> >Object Model". I had opened this JIRA after a suggestion on dev list.
> >However I must acknowledge that I never understood the need/importance 
of
> >this.
> >
> >Can someone help me by throwing some light on this? What is expected 
and
> how
> >would that be useful?
> >
> >Thanks,
> >Shiva Kumar H R
>
>
>


Reply via email to