We had the same problem. Personally I don`t have much problems with the complexity of Tapestry, but I can`t speak for the whole team. That is why we are going to use Wicket (99% chance). Tapestry and Wicket look the same (on the surface) and the both have a lot of the same options but wicket is a lot cleaner (no more page file and no more extracting/inserting content in pages). I think Tapestry is getting a littlebit bloated/draging along to much garbage.
If Tapestry could start over, I would love to see what they could make of it. BTW: Hibernate can be a nightmare. It is difficult to get the session problems right. We have been discussing various session strategies for more than a month, and finally came up with something usefull. The biggest problems with sessions are the many ways you can deal with them, and that it is difficult to find others with similar problems. We are glad it works and I`m glad I can reason about what is going on. And if you throw Spring next to Hibernate/Tapestry(or Wicket) you have a nice combination. Hibernate for the or-mapping. Tapestry for the visual aspect, and Spring glueing everything together. -----Oorspronkelijk bericht----- Van: Varun Mehta [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 12 augustus 2005 9:07 Aan: [email protected] Onderwerp: Back to Tapestry after an Year 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
