[jboss-dev-forums] [Design of JBoss Portal] - Re: hibernate session handling

[julien@jboss.com]

This is done programmatically in org.jboss.portal.jems.hibernate.SessionFactoryBinder


  |       // Force transaction manager lookup class and JTA env
  |       setPropertyIfAbsent("transaction.auto_close_session", "true");
  |       setPropertyIfAbsent("transaction.flush_before_completion", "true");
  |       setPropertyIfAbsent("hibernate.transaction.flush_before_completion", "true");
  |       setPropertyIfAbsent("hibernate.transaction.factory_class", "org.hibernate.transaction.JTATransactionFactory");
  |       setPropertyIfAbsent("hibernate.transaction.manager_lookup_class", "org.hibernate.transaction.JBossTransactionManagerLookup");
  | 

Transaction demarcation occurs in the server interceptor org.jboss.portal.core.aspects.server.TransactionInterceptor.java, the transaction demarcation is delegated to a JBoss AOP aspect which applies on the TransactionInterceptor, found in portal-aop.xml


  |    <metadata
  |       tag="transaction"
  |       class="org.jboss.portal.core.aspects.server.TransactionInterceptor">
  |       <method name="invoke">
  |          <trans-attribute>RequiresNew</trans-attribute>
  |       </method>
  |    </metadata>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079546#4079546

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079546