Another difference: in tapestry-rss, you don't need to care on how to
include the link to the feed in the header: a mixin already does that for
you. In addition, you don't need to worry about creating a page or event
to return the feed: tapestry-rss provides one out-of-the-box (/rss). You
just need to implement a ChannelProvider, which receives the RSS page
activation context and returns a Channel instance (class already included
in tapestry-ioc), and contribute it to the ChannelProvider Tapestry-IoC
service. This is how you'll provide the RSS channels and items for
tapestry-rss.
On Sun, 06 Oct 2013 15:56:20 -0300, Thiago H de Paula Figueiredo
<thiag...@gmail.com> wrote:
On Sun, 06 Oct 2013 13:15:51 -0300, Michael Gentry
<mgen...@masslight.net> wrote:
BTW, I hope I didn't sound negative. I was just pointing out a similar
project (which hasn't been updated in a while) and maybe there are good
ideas in it, etc.
Hello, Michael!
It didn't sound negative at all. :) I did the same research you did
before choosing to implement my own RSS support and create a second
package to do the same thing just for the sake of it would be a waste of
time. My original plan was to use tapestry5-rome, but some reasons made
me decide otherwise:
* tapestry5-rome isn't in the Maven Central Repository, so it would make
it hard for people wanting to use, customize and fork Eloquentia (my
blog engine, which powers machina.com.br, which I'll talk about in
another thread).
* tapestry5-rome has a dependency on Rome, tapestry-rss has a dependency
on Tapestry and nothing else.
* RSS is actually a simple format and I knew I could implement it
quickly.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
