Just to add my two cents. My tapestry applications have been in production for a long time (7+ years) and are rock solid and highly scalable. I think Tapestry is still a very good solution for many use cases.
Thanks Taha > On 28 Nov 2018, at 00:26, Thiago H. de Paula Figueiredo <thiag...@gmail.com> > wrote: > > On Tue, Nov 27, 2018 at 11:39 AM Mats Andersson <mats.anders...@ronsoft.se> > wrote: > >> I have been using Tapestry in different setups since the beginning of >> Tapestry 5. First I found the IOC and the client components useful. > > > In my day job, which uses Tapestry, even the people who dislike > Tapestry-the-web-framework actually like Tapestry-IoC very much. > > >> Then I realized the benefits of the genious way the filters works. > > > Yes, you can handle, decorate and protect with Tapestry's filters even > requests which aren't served by Tapestry itself. I'd also include the > dispatchers too. Similar to servlets, but way better (live class reloading, > no XML configuration, Tapestry-IoC). > > >> Now if not already done, in my opinion, it is time to separate client and >> server parts. > > > I'm not sure what's your line between client and server. Client usually > includes just JavaScript, but your description seems to include pages and > components too. If you mean a Tapestry-minimal framework including just > RequestFilter and Dispatcher, that's doable, not a huge effort, and > something similar was already done in the past without breaking changes > (separating the BeanModel classes from tapestry-core). > > >> The main problems I would say is the lack of an updated best practices > > > Well, the best practices are the same since Tapestry 5.4 was released, and > I'm saying that specifically due to the change in JavaScript support. The > rest hasn't changed much since Tapestry 5.0. > > >> and the missing Java 11 support. > > > It's being worked on right now, starting with Java 9 first, then 10 and 11 > to follow. > > >> I am not updated with the latest on Java 11 support but for my own sake I >> am not that worried. About the best practices it is mainly a problem for >> Tapestry acceptance. When people see that pages are rendered server side in >> Tapestry they see a conflict with the powerful way to build web >> applications using Angular or similar. What they don't see is the beautiful >> backend framework that is so complete that it do not require continuous >> updates. Just opinions, but hopefully it will be of use to someone. >> > > Thanks for your insights! > > -- > Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
