[
http://jira.jboss.com/jira/browse/BPEL-196?page=all ]
Alejandro Guizar updated BPEL-196:
----------------------------------
Workaround Description:
1. Extract the attached patch to BPEL_HOME.
- lib/jbpm/jbpm-identity-3.1.1.jar
- src/bpel/org/jbpm/bpel/data/exe/varmapping.xml
- src/config/jbpm.cfg.xml
- src/config/hibernate.cfg.xml
- build.xml
2. Rebuild the bpel library and service by calling targets build, build.service.404 in
BPEL_HOME/build.xml
3. Build the jBPM web application by calling target build.webapp in
JBPM_HOME/build.deploy.xml
4. Deploy BPEL_HOME/build/jbpm-bpel.sar and then JBPM_HOME/build/jbpm.war to JBoss
If you start JBoss at this point, you will no longer see the messaging service error. You
will see the web app show up but you won't be able to use it since the users table is
empty. You might want to perform the steps below to load some users and the sample websale
process into the HSQL database that jBPM BPEL uses by default.
EITHER
5. Copy the following files from BPEL_HOME to JBPM_HOME/lib/bpel/:
- build/jbpm-bpel-xxx.jar
- lib/commons/commons-lang-xxx.jar
- lib/wsdl4j/wsdl4j.jar
6. Copy hibernate.cfg.xml from BPEL_HOME/src/config to JBPM_HOME/src/config.files
7. Call target create.db in JBPM_HOME/build.deploy.xml
8. Rename localDB.* in JBPM_HOME/build/db to jbpmBpel.*
OR
9. Just grab the attached files.
10. Copy jbpmBpel.* to JBOSS_HOME/server/xxx/data/hypersonic
If you use a database other than the aforementioned, you can create the jBPM tables by
calling target create-schema in BPEL_HOME/doc/examples/build.xml
was:
1. Extract the attached patch to BPEL_HOME.
- lib/jbpm/jbpm-identity-3.1.1.jar
- src/bpel/org/jbpm/bpel/data/exe/varmapping.xml
- src/config/jbpm.cfg.xml
- src/config/hibernate.cfg.xml
- build.xml
2. Rebuild the bpel library and service by calling targets build, build.service.404 in
BPEL_HOME/build.xml
3. Build the jBPM web application by calling target build.webapp in
JBPM_HOME/build.deploy.xml
4. Deploy BPEL_HOME/build/jbpm-bpel.sar and then JBPM_HOME/build/jbpm.war to JBoss
If you start JBoss at this point, you will no longer see the messaging service error. You
will see the web app show up but you won't be able to use it since the users table is
empty. You might want to perform the steps below to load some users and the sample websale
process into the HSQL database that jBPM BPEL uses by default.
EITHER
5. Copy the following files from BPEL_HOME to JBPM_HOME/lib/bpel/:
- build/jbpm-bpel-xxx.jar
- lib/commons/commons-lang-xxx.jar
- lib/wsdl4j/wsdl4j.jar
6. Copy hibernate.cfg.xml from BPEL_HOME/src/config to JBPM_HOME/src/config.files
6. Call target create.db in JBPM_HOME/build.deploy.xml
7. Rename localDB.* in JBPM_HOME/build/db to jbpmBpel.*
OR
8. Just grab the attached files.
9. Copy jbpmBpel.* to JBOSS_HOME/server/xxx/data/hypersonic
If you use a database other than the aforementioned, you can create the jBPM tables by
calling target create-schema in BPEL_HOME/doc/examples/build.xml
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