[esb-issues] [JBoss JIRA] Closed: (JBESB-1060) The ESB throws NullPointerEception when there are no variables passed to jBPM process

Mark Little (JIRA) jira-events at lists.jboss.org
Sun Sep 23 16:16:11 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBESB-1060?page=all ]

Mark Little closed JBESB-1060.
------------------------------

    Fix Version/s: 4.2.1 IR1
       Resolution: Done

Added test for null Map.

> The ESB throws NullPointerEception when there are no variables passed to jBPM process
> -------------------------------------------------------------------------------------
>
>                 Key: JBESB-1060
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1060
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Process flow
>    Affects Versions: 4.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Little
>             Fix For: 4.2.1 IR1
>
>
> If you will not pass any variable but body when starting jBPM process then you will receive following exception
> org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor
>         at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127)
>         at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265)
>         at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.NullPointerException
>         at org.jboss.soa.esb.services.jbpm.actions.impl.facades.FacadeUtil.jbpmVarsToMessage(FacadeUtil.java:139)
>         at org.jboss.soa.esb.services.jbpm.actions.impl.facades.NewProcessInstanceFacade.postFormat(NewProcessInstanceFacade.java:84)
>         at org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProcessor.java:65)
>         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.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
>         ... 6 more
> The reason is that FacadeUtil expects that jBPM will return empty map when there are no variables in the context. Unfortuanetly for jBPM is valid to return even the null value when the variable list do not contain any variables.

-- 
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

        



More information about the esb-issues mailing list