[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 13:43 Message generated for change (Settings changed) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Closed Resolution: Out of Date Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Laurent Etiemble (letiemble) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-14 20:43 Message: Logged In: YES user_id=437455 I have re-read the spec. You were right. I will investigate on it. -- Comment By: Michael Hussey (mhussey) Date: 2003-10-13 22:23 Message: Logged In: YES user_id=357070 No it is not spec compliant, that was my point. You were throwing RollbackException in 2.4.4, not TransactionRolledbackException as the spec calls for. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 09:47 Message: Logged In: YES user_id=437455 It seems that this behaviour is spec compliant (see EJB 2.0 18.3.3). -- Comment By: Aparup Banerjee (aparup) Date: 2003-06-16 11:34 Message: Logged In: YES user_id=786442 Plz Assign This to me -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 18:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because quot;the bean method (ejbStore) runs in the context of the callers transactionquot;. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 18:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the clientamp;#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 15:43 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Laurent Etiemble (letiemble) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-14 22:43 Message: Logged In: YES user_id=437455 I have re-read the spec. You were right. I will investigate on it. -- Comment By: Michael Hussey (mhussey) Date: 2003-10-14 00:23 Message: Logged In: YES user_id=357070 No it is not spec compliant, that was my point. You were throwing RollbackException in 2.4.4, not TransactionRolledbackException as the spec calls for. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 11:47 Message: Logged In: YES user_id=437455 It seems that this behaviour is spec compliant (see EJB 2.0 18.3.3). -- Comment By: Aparup Banerjee (aparup) Date: 2003-06-16 13:34 Message: Logged In: YES user_id=786442 Plz Assign This to me -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 20:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 20:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 08:43 Message generated for change (Comment added) made by mhussey You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: Invalid Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Laurent Etiemble (letiemble) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Michael Hussey (mhussey) Date: 2003-10-13 17:23 Message: Logged In: YES user_id=357070 No it is not spec compliant, that was my point. You were throwing RollbackException in 2.4.4, not TransactionRolledbackException as the spec calls for. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 04:47 Message: Logged In: YES user_id=437455 It seems that this behaviour is spec compliant (see EJB 2.0 18.3.3). -- Comment By: Aparup Banerjee (aparup) Date: 2003-06-16 06:34 Message: Logged In: YES user_id=786442 Plz Assign This to me -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 15:43 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Closed Resolution: Invalid Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Laurent Etiemble (letiemble) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 11:47 Message: Logged In: YES user_id=437455 It seems that this behaviour is spec compliant (see EJB 2.0 18.3.3). -- Comment By: Aparup Banerjee (aparup) Date: 2003-06-16 13:34 Message: Logged In: YES user_id=786442 Plz Assign This to me -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 20:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 20:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 17:43 Message generated for change (Comment added) made by aparup You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Aparup Banerjee (aparup) Date: 2003-06-16 15:34 Message: Logged In: YES user_id=786442 Plz Assign This to me -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 22:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 22:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 08:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 08:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 08:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Hussey (mhussey) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
