Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://static.springsource.org/spring/docs/current/reference/transaction.html#transaction-declarative-annotations" rel="noreferrer">http://static.springsource.org/spring/docs/current/reference/transaction.html#transaction-declarative-annotations</a></p> <blockquote> <p>In proxy mode (which is the default), only external method calls coming in through the proxy are intercepted. This means that self-invocation, in effect, a method within the target object calling another method of the target object, will not lead to an actual transaction at runtime even if the invoked method is marked with @Transactional.</p> <p>Consider the use of AspectJ mode (see mode attribute in table below) if you expect self-invocations to be wrapped with transactions as well. In this case, there will not be a proxy in the first place; instead, the target class will be weaved (that is, its byte code will be modified) in order to turn @Transactional into runtime behavior on any kind of method.</p> </blockquote> <p>The <code>@Autowired</code> reference <code>B b</code> (inside class <code>A</code>), is wrapped with a Spring AOP transaction-aware proxy. </p> <p>When <code>b.inner()</code> is called, you are invoking it on the transaction-aware instance, and it is marked as <code>@Transactional</code>. Thus a Spring managed transaction is started. </p> <p>When <code>b.outer()</code> is called, it is also on a transaction-aware instance, but it is <strong>not</strong> <code>@Transactional</code>. Thus a Spring managed transaction is <strong>not</strong> started.</p> <p>Once you are inside the invocation of <code>outer()</code> the call to <code>inner()</code> is <strong>not</strong> going through the transaction-aware proxy, it is being invoked directly. It is the same as <code>this.inner()</code>. Since you are invoking it directly, and not through the proxy, it does not have the Spring transaction-aware semantics. </p> <p>Since no transaction has been started, this results in the <code>TransactionRequiredException</code>.</p> <p>Possible solutions include making the method <code>outer()</code> <code>@Transactional</code>.</p> <pre><code> @Transactional public void outer() { inner(); } </code></pre> <p>Or making the entire class <code>@Transactional</code>.</p> <pre><code>@Transactional @Component class B { @PersistenceContext EntityManager em; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIndirect Hibernate/JPA method call loses transaction
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDan
    1. USDan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIndirect Hibernate/JPA method call loses transaction
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMy goal was to create a background program and commit small bits each time. So annotating outer() as a singular transaction is not my intent. I'm off changing proxy mode to aspect-j mode. Thanks!
      singulars
      1. PO
      1. USCojones
    2. COIf the logic in `B.outer()` needs to happen before `B.inner()` but is not involved in transaction/persistence, it likely doesn't belong in your persistence layer classes (DAL/DAO etc). Consider refactoring your design to separate the concerns, possibly though use of an intermediate object. `Object intermediate = b.outer(); b.inner(intermediate);`. And then refactor, so that it is no longer a member of your persistence layer classes. `Object intermediate = someOtherUtilityOrSupportClassInstance.outer(); b.inner(intermediate);`.
      singulars
      1. PO
      1. USDan
    3. COI've switched to LTW now, but i'm getting no transaction in any call now :( All config is added <context:annotation-config/>, <tx:annotation-driven mode="aspectj".., <context:load-time-weaver aspectj-weaving="on" and TomcatInstrumentableClassLoader, etc. Are you sure it's possible? This post thinks JPA/Hibernate/LTW can't be done: http://stackoverflow.com/questions/2536292/how-to-run-spring-3-0-petclinic-in-tomcat-with-hibernate-backed-jpa "load-time weaver SHOULD NOT be used with Hibernate, this is for Toplink)" Or do i need compile time weaving?
      singulars
      1. PO
      1. USCojones
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload