Hello all, It's been a long time since i've last posted. Been pretty happily working with restlet 1.1 for some time now. I've come across an issue/optimization that i'm trying to solve that i'd like to get your thoughts on.
We are using Spring's AOP and Transaction Management to handle a lot of our database access. This has greatly simplified our code and we're loving it. Right now we apply the @Transactional annotation for each of the functions in the resource class. Therefore the init function has it, acceptRepresentation has it and so on. The init function will initially pull the resource in one transaction and the subsequent method handlers potentially open a second transaction to further process changes. The issue for us is that we are trying to keep the original select and update calls in the same transaction to ensure transactional integrity. The only way I know of to make this work is to put the @Transactional annotation at a higher level so that the transaction is open for the entire life of the resource handler execution. Unfortunately I have been unable to find a way to do this with restlet. How can I make @Transactional to take affect at a higher level than the resource? Is there a way to override the resource router or is there some already built-in mechanism that I need to enable or set up? Thanks in advance, Jean-Philippe Steinmetz ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2429858
