also at some places I see e.printStackTrace() in the catch block. Is there any specific reason why we are printing the stack trace at some places, whereas throwing an OpenEJBException at some other places? What is the general exception handling strategy?
On 1/7/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Jan 7, 2007, at 9:05 AM, Karan Malhi wrote: > While writing a patch for OPENEJB-434, I found out that the > JarUtils class > tries to use a Messages.properties file under > org.apache.openejb.util.resources package. I could not find this > properties > file in there. Maybe i have not understood exception handling fully > here, > but would there be any other location it would find the > Messages.propertiesfile. That properties file is here: http://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb3/ container/openejb-core/src/main/resources/org/apache/openejb/util/ resources/Messages.properties There all under src/resources as maven doesn't like them under src/java -David
-- Karan Malhi
