The recurring theme I've gotten from my many clients is that they looked at JSF and looked at Tapestry and saw Tapestry as the clear winner.
JSF demos well, and its goals are good, and its a newer code base. However, once you get past demos and prototypes, it ends up being quite a bit of coding. Facelets, which adapts some Tapestry ideas to JSF, is a big help, as it makes it easier to create custom components ... but does so at the expense of incompatibility with the JSF IDEs, which require you to stick with the default, JSP based view stack. There are quite a number of Tapestry developers in the UK and in Europe. As to professional support, take a peek at http://tapestrysupport.com. Tapestry has excellent integration with portlets. Compatibility, and the lack thereof, between Tapestry 4 and Tapestry 5 is an issue. I've controversially stated that compatibility is at best a secondary issue. I've already been able to accomplish some amazing things in the Tapestry 5 code base because I'm not trying for backwards compatibility: this includes POJO classes and automatic class reloading. The basic concepts of Tapestry 4 will carry forward to Tapestry 5, but the implementation is completely different. I've been accused of not caring about backwards compatibility, but the reality is that I do care about it, and I've been facing the conflict between adding features and breaking compatibility with each new release of Tapestry. Tapestry 5 rewrites those rules so that it will be quite reasonable to add features without breaking existing code. On 9/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hello everyone, this question goes to main team that developer the core of tapestry. I'm currently working in big company (7.000+ employees) and we are in the way to think about update our J2EE environment and frameworks. Im including in that big "brainstorm" in particular on the web and portal applications, and about the presentation framework we have allot of doubts and we currently have to choices in mind Tapestry and JSF, I have done some research with tapestry and jsf, i like allot tapestry over jsf, and i have few question that i should like to have some answers, to have more arguments to select the best for my company. - The components parts are very important for us, i want to know the experience from the team and users about the incorporate with portals (portlet's, now its native) - VERY important THING, and the issues. - Other important thing its about the compatibility of version (think this may be one of the big causes not bigger success on this framework), if we go to T4 how the core team think to maintain the compatibility of T4 apps in T5? - About support, how its works? do Tapestry community have support in Europe? (Portugal), and if yes how can we have some courses? I hope that somehow everyone on this community can help to answer my questions. Thanks for all reading me. Best regards, Fernando Pereira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
