RE: Jelly Integration

"Aapo Laakkonen" <[email protected]>
Newsgroups gmane.comp.web.maverick.general
Organization ProjectCast Oy
Message-ID <000b01c302c7$332bc5c0$1d9dedc3@bungle>
> As Aapo pointed out in a private conversation,
> the Jelly Servlet (that is modelled after Velocity
> Servlet) that is distributed in the standard Jelly
> package should function fine. There's no itch for
> me working out an example as I am not using nor
> plan on using Jelly in the near future. I can
> imagine it being handy if you develop XML centric
> apps where you want to have the option of using
> pull behaviour, but right now I am very pleased
> with Velocity.

You are right. I looked at Jelly integration one day, but I had problems
with it. Mainly the JellyServlet was not working as expected. It looks
like we should give some more time for Jelly to mature.

I don't right now want to spend too much time for it (Jelly) as there is
already very good alternatives that I already have got working with
Maverick (XSLT, Domify, Velocity and Freemarker).

Eelco, should we look back at it when Jelly developers get the version
1.0 released?


Regards
Aapo Laakkonen



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
[INVALID FOOTER]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.