Enterprise WebBeans w/ PersistenceContext throw incorrect exception when failing -------------------------------------------------------------------------------- Key: WBRI-275 URL: https://jira.jboss.org/jira/browse/WBRI-275 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.PREVIEW1 Environment: Suse 11.1 and SLES 10.2 Java 6 64 Bit JDK JBoss AS 5.1 Reporter: John Ament Priority: Minor If you create an enterprise web bean with a logical error, i.e. attempting to play with the transaction from within a method or attempt to access a table that does not exist, you get a stack trace that only mentions: java.lang.IllegalArgumentException: enterpriseBeanInstance.setDestroyed() called with non-boolean argument This is incorrect, or at least undesirable, because there's no clear indication where the error actually lies. Examples of the poor programming: Referencing an entity bean that has @Table("some_non_existent_table") Starting a transaction: entityManager.getTransaction().begin(); Query q = entityManager.createQuery("select i from Image i where i.skuAssociated = :sku").setParameter("sku", sku); List<Image> results = q.getResultList(); entityManager.getTransaction().commit(); return results; Essentially, anything that can cause a RuntimeException (or child of) to be thrown from within the methods of a Stateful EJB. To test: Create a standard EJB w/ a similar programming problem and see that it does not throw this exception. Create an enterprise web bean w/out this programming problem and see that it does not throw this exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira