[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2312) NPE when using JBPM in Seam without a DbPersistenceServiceFactory confirgured

[David Heggie (JIRA)]

NPE when using JBPM in Seam without a DbPersistenceServiceFactory confirgured
-----------------------------------------------------------------------------

                 Key: JBSEAM-2312
                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2312
             Project: JBoss Seam
          Issue Type: Bug
          Components: BPM
    Affects Versions: 2.0.0.GA
            Reporter: David Heggie
            Priority: Minor


I have noticed that when using JBPM with Seam, a DbPersistenceServiceFactory must be configured in the jbpm.cfg.xml, otherwise a NullPointerException occurs. I know that you can run JBPM by it self without persisence configured and it works just fine.

Is there a specific reason why JBPM must be configured with a persistence service in Seam. If not, there is a simple null check that can be done in the org.jboss.seam.bpm.Jbpm.initJbpmConfiguration() method to fix my problems.

Also the Jbpm class has a few dependancies on Hibernate that would be nice to remove as it is annoying to include the whole jar just for 2-3 classes. 

Stacktrace:

INFO  27-11 16:18:00,430 [org.jboss.seam.contexts.Contexts.startup():303] starting up: org.jboss.seam.bpm.jbpm
INFO  27-11 16:18:00,524 [org.jbpm.JbpmConfiguration.getInstance():277] using jbpm configuration resource 'jbpm.cfg.xml'
27-Nov-2007 16:18:00 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
java.lang.NullPointerException
	at org.jboss.seam.bpm.Jbpm.initJbpmConfiguration(Jbpm.java:129)
	at org.jboss.seam.bpm.Jbpm.getJbpmConfiguration(Jbpm.java:93)
	at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:245)
	at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:72)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
	at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
	at org.jboss.seam.Component.callComponentMethod(Component.java:2074)
	at org.jboss.seam.Component.callCreateMethod(Component.java:1997)
	at org.jboss.seam.Component.newInstance(Component.java:1968)
	at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
	at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
	at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:95)
	at org.jboss.seam.init.Initialization.init(Initialization.java:555)
	at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
	at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
	at org.apache.catalina.core.StandardService.start(StandardService.java:516)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)	

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira