<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>As some of you may know I've started looking at the transactions and persistence module. To start with I am just going to port what we had in seam 2, and we can work form there. I have already ported the UserTransaction wrapper stuff and the transaction interceptor. Alternate UserTransaction wrappers can be specified in seam XML (e.g. if you want to use HibernateTransaction).</div><div><br></div><div>I have changed the default to use EJB synchronisations (<transaction:ejb-transaction/> from seam 2), you will need to manually install SeSynchronisations in a non EJB environment. I will look at making the extension smart enough to detect this in most cases, so it will just work either way. </div><div> </div><div>I think that in a normal EE6 setup this module should not require a single line of XML, configuration should only be required if you are in a non-EE environment. </div><div><br></div><div>I that the SMPC should be configured with an annotation on a producer field, something like:</div><div><br></div><div>@Produces</div><div>@ManagedPersistenceContext</div><div>@PersistenceContext</div><div>@ConversationScoped</div><div>EntityManager entityManager;</div><div><br></div><div>I don't think we should override the behaviour of every resource producer field by default, and xml configuration should also be supported. </div><div><br></div><div>Questions:</div><div><br></div><div><b>Do we want to allow @TransactionAttribute to be used on managed beans (as well as @Transactional)?</b></div><div><b><br></b></div><div>I think we should do this. Also there was talk of changing the names used in the seam provided annotation, is that still on the cards (personally I am very much against this)? </div><div><br></div><div><b>Are we still going to provide seam equivalents of the EE API's (e.g. @ApplicationException etc)? </b></div><div><br></div><div>I'm guessing yes.</div><div><br></div><div><b>Seam 2 allowed you to use seam-jndi.properties to specify JNDI properties</b></div><div><b><br></b></div><div>Are we going to do something like this? If so where at. </div><div><br></div><div><b>Are we going to support REQUIRES_NEW for managed beans?</b></div><div><b><br></b></div><div>I really want this. It will probably only be availible in a JTA environment though, and will probably require XML configuration in some cases.</div><div><br></div><div><b>Are we going to stop the ManagedPersistenceContext from propagating across the transaction boundary for REQUIRES_NEW transactions?</b></div><div><b><br></b></div><div>I think that in this situation:</div><div><br></div><div>@Stateless</div><div>public class MyEJB</div><div>{</div><div> @Inject EntityManager entityManager;</div><div><br></div><div> @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)</div><div> public void doStuff()</div><div> {</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>entityManager.createQuery(...);</div><div> ...<span class="Apple-tab-span" style="white-space:pre"> </span></div><div> }</div><div>}</div><div><br></div><div>we should inject a new EM rather than one that is enlisted in the outside transaction. We could also provide a TransactionScoped em, but that does not solve the problem in the following situation:</div><div><br></div><div><div>@Stateless</div><div>public class MyEJB</div><div>{</div><div> @Inject HelperBean helper;</div><div><br></div><div> @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)</div><div> public void doStuff()</div><div> {</div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>helper.doStuff()</div><div> }</div><div>}</div></div><div><br></div><div>public class HelperBean {</div><div><br></div><div> @Inject EntityManager entityManager;</div><div> public void doStuff() {};</div><div>}</div><div><br></div><div>I think that we should maintain a stack of EM's in the Managed Persistence Context, and push a new one when we cross a transaction boundary, so all em calls after than point are invoked on a new EM. This is a real problem, and there are heaps of posts about this in the seam 2 forum.</div><div><br></div><div><b>Where do seam managed transactions belong?</b></div><div><b><br></b></div><div>Probably the faces module. </div><div><br></div><div><b>Do we want to support multiple RESOURCE_LOCAL transactions?</b></div><div><b><br></b></div><div>There have been quite a few posts on the forum about this, but I don't know if it really makes sense. You would need some way of telling the transaction interceptor which UT it is supposed to use. Seam managed transaction would probably have to work on both transactions, wether they are needed or not. </div><div><br></div><div>Does all this sound ok? If so I will write this stuff up on the module page and start implementing.</div><div><br></div><div>Stuart</div><div><br></div><div><br></div><div><br></div></body></html>