[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
noon
ManagedPersistenceContext.getEntityManager() should not throw NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
12:06 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=comments#action_12363401 ]
Michael Youngstrom commented on JBSEAM-1363:
--------------------------------------------
We may even want to consider not throwing a SystemException either since this method is
the @Unwrap method and would make catching this exception by a client to a
ManagedPersistenceContext difficult.
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
4:30 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=all ]
Gavin King closed JBSEAM-1363.
------------------------------
Resolution: Rejected
A generic, unknown failure accessing the naming service is definitely not the same thing
as there being no transaction. I don't want to change this.
Exceptions thrown out of @Unwrap methods get wrapped in RuntimeExceptions, and can be
handled in pages.xml.
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
4:42 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=comments#action_12363461 ]
Michael Youngstrom commented on JBSEAM-1363:
--------------------------------------------
Just for the record this is another hurdle in trying to get Seam to "get out of the
way" with regards to Transaction management. Another way to handle this issue is if
TransactionManagement were made a component that could be turned off. (see JBSEAM-1144)
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
4:47 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=comments#action_12363462 ]
Gavin King commented on JBSEAM-1363:
------------------------------------
Yes, I understand that, and I am +1 on making the Transactions class a Seam component.
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
5:01 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=comments#action_12363464 ]
Michael Youngstrom commented on JBSEAM-1363:
--------------------------------------------
That's good to hear.
Unfortunately since JBSEAM-1144 isn't scheduled until 1.3.1 I'm going to have to
figure out some other way to use Seam Managed PersistenceContexts in my environment where
I cannot get a UserTransaction through JNDI. :) I'll figure out something.
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
5:16 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=comments#action_12363468 ]
Gavin King commented on JBSEAM-1363:
------------------------------------
It says "Fix Version/s: 1.3.0.BETA1"
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
5:22 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1363) ManagedPersistenceContext.getEntityManager() should not throw NamingException
[ http://jira.jboss.com/jira/browse/JBSEAM-1363?page=comments#action_12363470 ]
Michael Youngstrom commented on JBSEAM-1363:
--------------------------------------------
Oh, I'm an idiot. :) version "1.3.1.BETA1" must have been renamed to
"1.3.0.BETA1" after it was pushed back or something. Anyway, thanks I'm
good now.
ManagedPersistenceContext.getEntityManager() should not throw
NamingException
-----------------------------------------------------------------------------
Key: JBSEAM-1363
URL: http://jira.jboss.com/jira/browse/JBSEAM-1363
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Fix For: 1.3.0.ALPHA
ManagedPersistenceContext.getEntityManager() has the potential to throw a NamingException
because of a call to Transactions.isTransactionActive(). I believe
ManagedPersistenceContext.getEntityManager() should assume that a NamingException thrown
from Transactions.isTransactionActive() equates to "false".
My guess is the "throws NamingException" might be a relic of obtaining an
EntityMangager from an EMF obtained through JNDI. However, that has moved to
initEntityManager() that handles the error of obtaining an EMF on it's own. So, I
think getEntityManager should log a NamingException thrown from
Transactions.isTransactionActive() and move on as if no transaction is active.
Mike
--
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
6889
days inactive
6889
days old
7 comments
2 participants
participants (2)
-
Gavin King (JIRA) -
Michael Youngstrom (JIRA)