Sorry for the delay. I've put my code for this on the wiki: http://wiki.apache.org/jakarta-tapestry/EmittingRSSFeeds. It's pretty raw, but I hope it helps.
jeff -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Raul Raja Martinez Sent: Friday, February 17, 2006 9:05 PM To: [email protected] Subject: Re: Best practices to output a RSS feed Yes, I'd love to see some code, right now the approach I'm following is having the rss xml file inside the page.html template and simply iterating throught the objects I need to generate the rss. I'm changing the response to set the content-type to xml. The Channel and items objects are in a database so in the future I would probably just generate an XML file in a Hibernate EvenListener so that people access a static xml file for the feed instead of having the RSS generated by tapestry. Jeff Lubetkin wrote: > While I don't have any code to share right now, and haven't heavily tested this in a production/heavy load environment, I have had good luck using the ROME library (https://rome.dev.java.net/) to both generate and consume RSS feeds in Tapestry. For generation, I created Feed and Entry components, and used the page service to serve them up like any other page. The trickiest bit (thought not incredibly hard) was having the Entries render into buffers and be appended to the parent Feed. > > If you'd like, I can probably share some code next week when I'm back at the office. > > jeff > > ________________________________ > > From: news on behalf of Raul Raja Martinez > Sent: Fri 2/17/2006 6:02 PM > To: [email protected] > Subject: Best practices to output a RSS feed > > > > I was wondering what are the best practices in tapestry to output a RSS > document. > > I was thinking either: > > Custom EngineService that outputs to the HttpServletResponse > > or a page using the xml as a template. > > best regards. > > Raul. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
