[jboss-jira] [JBoss JIRA] Resolved: (BPEL-196) jbpm and bpel services do not play together well

[Alejandro Guizar (JIRA)]

     [ http://jira.jboss.com/jira/browse/BPEL-196?page=all ]

Alejandro Guizar resolved BPEL-196.
-----------------------------------

    Resolution: Done

Applied the configuration changes contained in the patch to the head branch. Beta 2 will include the jBPM identity component and add it to the BPEL service archive for compatibility with jPDL processes. End users will still be responsible for building and deploying the jBPM web console separately. 

Writing a section in the user guide describing how to build and deploy the jBPM web console will be tracked in a separate issue.

> jbpm and bpel services do not play together well
> ------------------------------------------------
>
>                 Key: BPEL-196
>                 URL: http://jira.jboss.com/jira/browse/BPEL-196
>             Project: JBoss jBPM BPEL
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 1
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>            Priority: Critical
>             Fix For: jBPM BPEL 1.1 beta 2
>
>         Attachments: jbpm-bpel-1.1-beta1-bpel-196.zip, jbpmBpel.properties, jbpmBpel.script
>
>
> When deploying a jPDL process or even accessing the jbpm web application, the following exception arises:
> java.lang.NullPointerException
>         at org.jbpm.JbpmContext.setActorId(JbpmContext.java:453)
>         at org.jbpm.web.JbpmContextFilter.doFilter(JbpmContextFilter.java:81)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>         at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
>         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
>         at java.lang.Thread.run(Thread.java:595)

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