Ted Steen wrote:
I think I need to read up on those TransactionInterceptors and engine services :) If you got some good reading on these topics I would be glad to have a look at it.
These are some of the services you can intercept, I've been thinking about intercepting the Page (and related) service(s) to take care of authentication in a system I'm developing at the moment.
http://jakarta.apache.org/tapestry/tapestry/hivedocs/module/tapestry.services.htmlThis is the HiveModule element used to intercept already existing services with:
http://jakarta.apache.org/hivemind/descriptor.html#interceptorAnd this is the HiveTranse quick start section about transaction handling via method interception:
http://hivetranse.sourceforge.net/quickstart.html#start.config.transaction
What do you think of the whole HibernateSqueezer idea? in order to unsqueeze I need a transaction started when the unsqueezing is taking place. maybe that is done with the interceptors and engine services?
To be honest I haven't looked at the HibernateSqueezer yet, but I guess I will have to do that in a moment. Again, it wouldn't really be a problem for me because I use the session-per-request pattern, so as soon as I need a Session it will be opened by my SessionManager service and then stay open until I close it or the request ends, whichever comes first.
If the unsqueezing is done by a service you could defintely intercept that service providing a TransactionInterceptor instance on the unsqueezing method.
I am taking my first trembling steps into the db-layer, transaction handling world and I obviously need some guidance.
Hehe, I'm actually just a 19-year old upper-secondary school student myself and only recently delved into transaction handling and stuff.
I'm sure people on both the Tapestry and HiveMind user lists will be happy to help if you have any further questions, though - I know I'll do what I can.
Regards, Filip
smime.p7s
Description: S/MIME Cryptographic Signature
