sorry that meant to say 'custom runtime exception subclasses'. Chris Christo
--- Twitter: https://twitter.com/ChrisChristo7 Tumblr: http://chrischristo7.tumblr.com LinkedIn: http://uk.linkedin.com/in/chrischristo GitHub: https://github.com/ChrisChristo On 30 May 2013, at 12:14, "Chris.Christo" <[email protected]> wrote: > Just a question I have related to this; > > Why do your own customer runtime exception subclasses get wrapped in an > EjbException when the ejb beans are local? > Surely the caller will have the exception class in its classpath? > > Chris Christo > > --- > Twitter: https://twitter.com/ChrisChristo7 > Tumblr: http://chrischristo7.tumblr.com > LinkedIn: http://uk.linkedin.com/in/chrischristo > GitHub: https://github.com/ChrisChristo > > On 30 May 2013, at 07:19, vhubuo <[email protected]> wrote: > >> Yes. The RuntimeExceptions are wrapped into EJBException for the client. And >> I see the stack trace on client. But I don't see the stack trace in any of >> server log files. >> >> So my question is how does TomEE log unexpected exceptions in stateless >> beans exposed via remote annotation ? And is there any configuration >> available. >> >> I use a "clean" installation of 1.5.2 of the server without any >> configuration. >> >>> can you check with the snapshot, i just tried with 1.6.0-SNAPSHOT >> >> On 1.6.0-SNAPSHOT it works correctly. >> >> I get: >> май 30, 2013 9:14:57 AM >> org.apache.openejb.core.transaction.EjbTransactionUtil handleSystemException >> SEVERE: EjbTransactionUtil.handleSystemException: user defined exception >> java.lang.UnsupportedOperationException: user defined exception >> >> What are your recommendations on production usage? >> >> >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/Remote-exceptions-logging-tp4663282p4663336.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >
