On 5/20/08, Christian Edward Gruber <[EMAIL PROTECTED]> wrote: > Wouldn't it be rather normal to create a tapestry-tx that provided > transaction wrappers around existing services, much the way tapestry-spring > and tapestry-hibernate do? Especially now that there's a bit more AOP going > on in T5.
I haven't tested the new Tapestry-IoC AOP features yet, but I think the answer is yes. But I don't expect it to be written by Howard. IMHO, he must focus on Tapestry-Core and Tapestry-IoC. Someone must do that. I even started something like that, but I headed in the wrong direction and now I'm focusing in writing some CRUD-related open source packages for Tapestry 5. I want to release them in the next weeks. I don't like the way tapestry-hibernate is implemented because, AFAIK, it violates the three-tier architecture (separation of persistence, business rules and user interface layers). Example: using Hibernate sessions in page classes. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
