FW: Barracuda vs. Tapestry

Just an FYI...Harish has graciously responded to my questions and I thought
folks on the list might be interested. I haven't had a chance to look at his
detailed doc yet...

Christian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

-----Original Message-----
From: Harish Krishnaswamy [mailto:[email protected]]
Sent: Tuesday, September 30, 2003 1:36 AM
To: Christian Cryder
Subject: Re: Barracuda vs. Tapestry


Hmm, it may be a little hard for me to describe it in a couple paragraphs,
but I'll try and you may edit it as you see fit.

Tapestry is a Java web component framework. A Tapestry component is a
building block that can be configured and composed to make other components.
A Tapestry page is also one such component with some exceptions. A
simple/basic component is made of an XML specification that defines the
parameters and other configuration, and a JavaBeans class that provides the
data and defines the behavior. Complex components (like the page) may have
an additional template (HTML/WML etc.) that could declare the usage of other
components which could be configured in the specification. Component
configurations can access the JavaBeans properties via OGNL (Object graph
Navigation Library). In Tapestry, Javascript can also make a component and a
component may also package Javascript with it.

A Tapestry application is a single controller servlet, an engine, a bunch of
services and components. There is provision to override/extend pretty much
everything. On first access of a page, the page object is built from the
template and specification and pooled after use. Any client state in the
page is automatically  managed by the framework. All URL manipulations are
handled by the framework services, all that the developers have to deal with
are objects.

I actually have a detailed (hopefully) document at
http://myworkspace.sourceforge.net that may provide a better understanding.

Before I came across Tapestry, Barracuda was the only framework I liked
although I was a short-lived user. The thing I liked about Tapestry better
than Barracuda was its conciseness, readily available off-the-shelf
components and is more my style. Honestly, Barracuda is a great product too,
and I am sure you already know!

Let me know if you need more info.

Regards,
Harish

Christian Cryder wrote:

Hi Harish,

Assuming that
a) this gets to you at this address, and
b) you are actually are the same "Harish Krishnaswamy" referenced here:
http://jakarta.apache.org/tapestry/quotes_frame.html

I'd love to hear how Barracuda compares to Tapestry. Pros? Cons? Would you
be willing to provide an architectural summary describing how Tapestry
works? (couple of paragraphs) I'd love to describe it more accurately here:
http://barracudamvc.org/Barracuda/docs/landscape.html

Regards,
Christian

----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"