Back to Tapestry after an Year

[Varun Mehta <va...@persistent.co.in>]

  Hi Fellas,

  I had studied Tapestry 3.0 beta, somewhere in
  Jan-Feb 2004, but could not go ahead and implement
  the same, as the learning curve for the team was a
  bit too high, and settled on for the Petstore
  application. Now I back in the same boat where I
  need to get back to a framework. The debate is b/w
  Struts - Webworks - Tapestry. I personally vouch for
  Tapestry cos it's cleaner for the HTML guys in the
  long run. Struts is something I want to avoid.

  I don't recall much of Tapestry. I was going through
  some sites and found the betterpetshop application
  based on Tapestry at
  https://betterpetshop.dev.java.net/, also at the
  same time found some criticizm on the project, as in
  it uses a lot of workarounds & does not implement
  Tapestry properly.

  http://www.jroller.com/page/cardsharp/Weblog?catname=%2FJava

    Tapestry is all about stateful user interactions. 
    It's designed to let you work with objects instead
    of request parameters. (This article assumes you
    WANT to work with objects instead of IDs.  Plenty
    of Tapestry apps just throw ID's around to get
    around the problems mentioned in this posting,
    e.g. the Better Petshop project.)  Hibernate is
    also about state.  It's about serializing object
    state into a relational database.  It's also very
    good at working with "detached" objects.  In other
    words, you can load persistent objects in one
    Hibernate session and reattach them during a later
    session.  You can even modify the object between
    sessions.

  Can anybody help me with the issue. Also I need a
  place where I can read an updated tutorial on the
  framework and train the team fast on it. The book
  'Tapestry in Action' is already issued out to
  someone else, so will take some time to be back in
  the library, meanwhile I need to study and give a
  presentation on 'WHY TAPESTRY'. The combination we
  are looking for is Tapestry + Hibernate.

  What I've read and feel is Tapestry +  Hibernate is
  Rocket fuel. If you take care and use it properly,
  you are in space, else a minor mistake and a mid-way
  boom!!..

  Please suggest. 


Regards
Varun Mehta
 - http://varun.cjb.net 
 - http://varuninfo.cjb.net 
 - http://varunmehta.cjb.net 


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
imagination is more important than knowledge – albert einstein
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Re: Back to Tapestry after an Year

[Ivano <i....@mclink.it>]

Maybe this could help:

http://www.agileskills2.org/EWDT/

Bye

Ivano Pagano.

Varun Mehta wrote:

>  Hi Fellas,
>
>  I had studied Tapestry 3.0 beta, somewhere in
>  Jan-Feb 2004, but could not go ahead and implement
>  the same, as the learning curve for the team was a
>  bit too high, and settled on for the Petstore
>  application. Now I back in the same boat where I
>  need to get back to a framework. The debate is b/w
>  Struts - Webworks - Tapestry. I personally vouch for
>  Tapestry cos it's cleaner for the HTML guys in the
>  long run. Struts is something I want to avoid.
>
>  I don't recall much of Tapestry. I was going through
>  some sites and found the betterpetshop application
>  based on Tapestry at
>  https://betterpetshop.dev.java.net/, also at the
>  same time found some criticizm on the project, as in
>  it uses a lot of workarounds & does not implement
>  Tapestry properly.
>
>  http://www.jroller.com/page/cardsharp/Weblog?catname=%2FJava
>
>    Tapestry is all about stateful user interactions. 
>    It's designed to let you work with objects instead
>    of request parameters. (This article assumes you
>    WANT to work with objects instead of IDs.  Plenty
>    of Tapestry apps just throw ID's around to get
>    around the problems mentioned in this posting,
>    e.g. the Better Petshop project.)  Hibernate is
>    also about state.  It's about serializing object
>    state into a relational database.  It's also very
>    good at working with "detached" objects.  In other
>    words, you can load persistent objects in one
>    Hibernate session and reattach them during a later
>    session.  You can even modify the object between
>    sessions.
>
>  Can anybody help me with the issue. Also I need a
>  place where I can read an updated tutorial on the
>  framework and train the team fast on it. The book
>  'Tapestry in Action' is already issued out to
>  someone else, so will take some time to be back in
>  the library, meanwhile I need to study and give a
>  presentation on 'WHY TAPESTRY'. The combination we
>  are looking for is Tapestry + Hibernate.
>
>  What I've read and feel is Tapestry +  Hibernate is
>  Rocket fuel. If you take care and use it properly,
>  you are in space, else a minor mistake and a mid-way
>  boom!!..
>
>  Please suggest. 
>
>
>Regards
>Varun Mehta
> - http://varun.cjb.net 
> - http://varuninfo.cjb.net 
> - http://varunmehta.cjb.net 
>
>
>*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>imagination is more important than knowledge – albert einstein
>*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org