[GERONIMO-691] OpenEJB Assumes Optional messaging-type is Present in ejb-jar.xml

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-M3
• Fix Version/s: 1.0-M4
• Component/s: OpenEJB
• Assignee: Aaron Mulder
• Reporter: Aaron Mulder
• Created: 02/Jul/05 15:53
• Updated: 07/Aug/06 15:05
• Resolved: 02/Jul/05 16:19

Description

OpenEJB barfs with an NPE if an MDB without a messaging-type set is deployed. That element is optional (defaults to JMS)

java.lang.NullPointerException
at java.net.URLClassLoader$1.run(URLClassLoader.java:190)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.openejb.deployment.MdbBuilder.initContext(MdbBuilder.java:142)
at org.openejb.deployment.OpenEJBModuleBuilder.initContext(OpenEJBModuleBuilder.java:313)