[
http://jira.jboss.com/jira/browse/JBSEAM-1900?page=comments#action_12379211 ]
Pete Muir commented on JBSEAM-1900:
-----------------------------------
The automatic detection in org.jbos.seam.transaction.Transaction.getTransaction() fails as
Tomcat (5.5 and 6) throws a NamingException not an NNFE when it can't access
java:comp/UserTransaction - in discussion with Mike Youngstrom and he said Gavin
explicitly didn't want to catch NamingException here. Mike and I concluded that the
best approach this was to make NoTransaction explicitly installable by the user.
However both of us feel that more review is required of this. Unless someone else can
review and say they are happy with this approach I propose deferring this until Gavin has
time to review.
org.jboss.seam.contexts.Contexts logs "could not discover
transaction status" even though transaction management is disabled
----------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-1900
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1900
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Reporter: Daniel Wiell
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.0.CR2
Attachments: JBSEAM-1900.diff
org.jboss.seam.contexts.Contexts logs "could not discover transaction status"
errors even though transaction management is disabled by the inclusion of the following in
components.xml:
<core:init transaction-management-enabled="false"/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira