Jacob (JSF):
"Tapestry: For a component framework, it still sticks to the page/action paradigm,
Because JSF isn't tied to the action/page paradigm, parts of the component tree
can be agnostically processed without requiring special cases/development."
is this really true about tapestry? Is it really that "static"?
Back in the days i worked with it ajax was not there so no requirement for it so
i don't know it anymore.
Geert (Rife):
"Wicket's strength is its pure Java approach, but that's also its crutch. Configuration and
declaration can't be summarized and waived away by stating that "XML sucks."
Huh? It is Java ! you can do everything. If you want xml configuration. Go ahead!
The total statement he makes is in my eyes ridicules.
Gavin (Seam): could like wicket if he makes this statement about tapestry:
"Very nice. The form validation stuff is *killer*! Templating approach was very innovative in
its time. The non-POJOness of the component model is a showstopper for me."
Tim (Stripes):
"If I were in a situation in which I needed to develop such an application for a client and the
client didn't want to use AJAX, I would probably look at Wicket. I've looked at Wicket
before (although not used it in anger) and am impressed with the quality and focus on
simplicity in the project."
He really should look again! Why does he think he can't use ajax?
The combination works great!
Howard over Tapestry 5: that looks a lot of wicket features :)
Interessting to see what the end result of for example this will be:
"Smart class loader; pick up changes to classes automatically and efficiently."
Because if you define youre own classloader in youre web app then nothing
that loads through that classloader can be stored as a serializeable thing in the session.
Patrick (WebWork):
"I've found that "HTML/CSS developers" and "app developers" rarely are separated
like Tapestry likes to pretend they are"
This is so not true.. i think i also heard this from Jason Carreira.
Almost every java developer i know (inclusing myself) are not very good designers..
The opposite. very good designer as absolutely no java developers
That specific kind of persons are very hard to find.
I guess its the way of thinking.
Eelco about tapestry: "and the templates are more flexible in use than are Wicket's."
Nice thing is that i just hear from a friend (and again a another friend of his who is
a tapestry user for a long time) that they really like the pages of wicket because
they are so flexible (dynamic)
johan
On 3/25/06, Eelco Hillenius <[EMAIL PROTECTED]
> wrote:
FYI, Matt Raible asked me to give my opinion about Wicket and some of
it's competitors. He presenting it tonight at the server side
symposium, and you can find his presentation here:
http://www.virtuas.com/articles/webframework-sweetspots.html
Eelco
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
