I mentioned this before in a different context. Hope this is not redundant.
I am looking to be able to wrap component events in transactions. I took a look at how the hibernate sessions are managed in tapestry-hibernate. Trouble with that model is that some of the code needs to be outside of a transaction. An example would be a JMS request that waits for a reply. If that happens in a transaction, the request won't be sent until the transaction is closed. Ideally, I would like to add my own @Transactional annotation around an event method and use something like a ComponentClassTransformWorker to enhance the class by wrapping the method invocation. Trouble is, I can't tell if that is possible using the ClassTransformation. Another option I looked at was to use a ComponentActionRequestFilter. What options do I have with Tapestry5 to do this? Any help would be appreciated. Ben
