jBPM does not create the schema's runtime (yet) there is a jira issue for this. So it is more of a problem of finding them. Do you use the same db as with the starterkit?
And with regard to 'getting different errors', please post them so I can try to help finding the cause.
I'll try to clearly specify my steps for the next person who will wish to attempt this trick. My ultimate goal is to make the console with with the jBPM embedded in the ESB 4.2 but for now I'm just shooting for AS 4.2.
- Plain vanilla AS 4.2 instance (no Messaging, no ESB, etc)
- jBPM 3.2.1 jPDL Suite download
1) Copied jbpm-console.war from the jbpm-jpdl-3.2.1\server\server\jbpm\deploy directory to my AS 4.2 default\deploy directory
2) removed the JSF & EI jars from the WAR's WEB-INF\lib
3) Copied jboss-backport-concurrent.jar from the jbpm-jpdl-3.2.1\server\server\jbpm\lib to my AS 4.2 server\default\lib directory
4) Copied jbpmDB.* from jbpm-jpdl-3.2.1\server\server\jbpm\data\hypersonic to
AS 4.2 server\default\data\hypersonic directory
Note: also tried building the schema by using the sql scripts found in jbpm-jpdl-3.2.1\db
5) Copied jbpm-ds.xml from jbpm-jpdl-3.2.1\server\server\jbpm\deploy to
AS 4.2 server\default\deploy
6) Start the AS instance via "run" from the bin directory.
7) Dig through the server.log to find:
ERROR [org.hibernate.proxy.pojo.BasicLazyInitializer] Javassist Enhancement failed: org.jbpm.taskmgmt.log.TaskAssignLog java.lang.RuntimeException: java.lang.IllegalArgumentException
So I need to modify the Hibernate related items in the jbpm-console.war it seems.
Or perhaps this is just going down the wrong path all together?
I decided to "cheat" and went back to CVS. The build script for the console makes a 4.2 compatible WAR where the primary differences seem to the following:
gravel-14.jar is now gravel.jar
So, that tells me this information is not completely accurate:
I suspect this was accurate for 3.2.0 but I can't verify that at this moment.
Another tip for anyone trying this at home:
Modify your AS login-config.xml to include the following -
<application-policy name = "jbpm"> <authentication> <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required"> <module-option name="dsJndiName">java:/JbpmDS</module-option> <module-option name="principalsQuery"> SELECT PASSWORD_ FROM JBPM_ID_USER WHERE NAME_=? </module-option> <module-option name="rolesQuery"> SELECT g.NAME_ ,'Roles' FROM JBPM_ID_USER u, JBPM_ID_MEMBERSHIP m, JBPM_ID_GROUP g WHERE g.TYPE_='security-role' AND m.GROUP_ = g.ID_ AND m.USER_ = u.ID_ AND u.NAME_=? </module-option> </login-module> </authentication> </application-policy>
But the results of my adventure basically show me that I need to go to CVS, build the console and use the 4.2 version of jbpm-console.war.
I've found 3 copies of jbpm-console.war in the jbpm-jpdl-suite-3.2.1 download. All have the gravel-14.jar which seems to be a problem.
I'm guessing this is related to Java version number and I'm running on JDK 1.5.
Bur, interesting topic, I'll try to verify this tonight (CET) with a fresh 4.2 download and the 3.2.1 and 3.2-cvshead
I am getting the same error... any clue?
sorry, I was not able to give this a try
If you don't wish to "build from source", I would suggest another trick (though untested). If you follow all the various steps outlined in this thread you'll note that I believe the problem is finally with gravel14.jar. If you go to jboss.org you can download gravel by itself and replace gravel14.jar with gravel.jar which I believe to be JDK 5 friendly.
@burr, just replacing gravel14.jar with gravel.jar isn't enough, it's also jbpm4jsf-14.jar that has to be replaced with jbpm4jsf.jar IMO
I'll do some more testing and put it up on a wiki when I'm through.
ERROR [JDBCExceptionReporter] Table not found in statement [select top ? job0_.ID_ as ID1_26_, job0_.VERSION_ as VERSION3_26_, job0_.
ERROR [JobSession] org.hibernate.exception.SQLGrammarException: could not execute query
ERROR [JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds
mException: couldn't get acquirable jobs
rg.hibernate.exception.SQLGrammarException: could not execute query