Regarding the original poster's statements: I think that Tapestry is so great because it does the job of an MVC really well. I hope that it doesn't become a "full stack" solution. I think it would be more beneficial to the community to ensure that Tapestry's focus is the MVC.
Additional functionality should be brought on through modules as some already are. Default security and transaction schemes will only become monsters of their own with devs requesting enhancements until quite a bit of Tapestry's development focus is shifted onto various sub-projects. And really, with all the fantastic frameworks out there - that are as good as they are because of focus - why carry the baggage of some interim scheme for developers not wanting to perform the minimal legwork of integration themselves? I think projects like tapestry-hibernate are nice because they eliminate common integration problems. But its job is to provide enhanced integration, not provide persistence for a Tapestry app. Personally, I don't use tapestry-hibernate because I am still one of those relics that believes having a properly tiered application is good architecture. Why should Tapestry care what persistence strategy I am using? Having said that, this module is nice for the quick app that doesn't need or desire the type of benefits that come with tiered development and greatly helps to integrate hibernate. More to the point, I believe that Howard and the Tapestry developers will be utilized as development resources most effectively if the focus remains on creating the #1 MVC framework. Thanks a million guys! Transactions declared in the Web tier? Oy vey. What's next, Tapestry-SOAP??? On 6/26/07, Joshua Jackson <[EMAIL PROTECTED]> wrote:
Dear all, I'm quite happy currently trying out T5 now. And I really like the T5 IoC concept compared to other IoC container. - I really like how it has (or will have) built in AJAX components. - I really like how easy it is to create custom components compared to other component based web framework. - I also like the integration with hibernate. It's just too damn simple and works out of the box. - I really like the GridPager component (though it got me struggle to work it out :P). I don't know any other web framework that has built in pager component. Everything just seems to be so natural and how a web framework should have been. But I have a questions here. With the so complete features that I have just mentioned, will Tapestry 5 have the vision to be a full stack framework in the future? Some features that I think will be great to be added if T5 will be a full stack framework is: - Built in security or user authentication and authorization. I must admit that using Acegi for the security is just unnecessary because I will need Spring just to get Acegi running. And I will have 2 IoC container in my apps. I think T5 IoC already have the features (like the decorator) to make security feature made available. - Built in declarative transaction, since there's already tapestry-hibernate module. I don't know whether this is possible, but when I read the T5 IoC decorator feature, I think I can start and end transaction before and after I invoke a method. Is it possible? Well that's my opinion and some ideas I came up with. Hopefully it can come true. And thank you so much for making T5. I can see that it will be a great framework in the future. Keep up the good work guys. Hats off for you people -- Let's create a highly maintainable and efficient code YM!: thejavafreak Blog: http://www.nagasakti.or.id/roller/joshua/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
