Humm, which @Transactional are you using? The one from the EJB spec? Some @Transactional from Spring or any JSR-299 Extension? Afaik there is no @Transactional annotation neither in the JPA spec nor in OpenJPA. In any case this is imo not a question which is directly determined by OpenJPA but by the interceptor of the framework you use.
So for being able to help you, the first thing is to determine _which_ @Transactional you are going to use ;) LieGrue, strub --- On Fri, 4/22/11, Masatake Iwata <[email protected]> wrote: > From: Masatake Iwata <[email protected]> > Subject: Question about @Transactional annotation. > To: [email protected] > Date: Friday, April 22, 2011, 9:00 AM > Hi, > > Please let me ask a question about the specification of > OpenJPA. > > 1. If @Transactional is given to a method when reading > entities from SQL > Server (a SELECT sentence is performed), a UPDATE sentence > will be performed > after execution of a SELECT sentence. Is this the > specification of OpenJPA? > > 2. Will it cause a problem if @Transactional is annotated > to a Read method, > (instead of Create, Update and Delete method)? > > 3. Is it a misuse to annotate @Transactional to Read method > ? > > 4. If many entities are persisted to a container > (EntityManager), without > flushing, does it finally hang by out of memory etc.? > > 5. When persisting multiple entities to the container > (EntityManager), is it > necessary to perform the flush > for a certain number of entities? if yes, how to define the > number of > entities. > > In addition, the version of Open JPA currently used is > 1.2.0. > > Thank you for your consideration. > > Masatake > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Question-about-Transactional-annotation-tp6296648p6296648.html > Sent from the OpenJPA Users mailing list archive at > Nabble.com. >
