build.deploy.xml - starters'kit

[mennen]

difference between build.deploy.xml and build.xml

Both files are in the starters' kit of jbpm.. The build.xml works fine when i execute it.. But the build.deploy.xml doesn't work at all, and gives me errors like :

java.sql.SQLException: socket creation error
[jbpmschema] at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
[jbpmschema] at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)
[jbpmschema] at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
[jbpmschema] at org.hsqldb.jdbcDriver.connect(Unknown Source)
[jbpmschema] at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:68)
[jbpmschema] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:87)
[jbpmschema] at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1.acquireResource(C3P0PooledConnectionPool.java:83)
[jbpmschema] at com.mchange.v2.resourcepool.BasicResourcePool.assimilateResource(BasicResourcePool.java:884)
[jbpmschema] at com.mchange.v2.resourcepool.BasicResourcePool.acquireUntil(BasicResourcePool.java:601)
[jbpmschema] at com.mchange.v2.resourcepool.BasicResourcePool.access$400(BasicResourcePool.java:31)
[jbpmschema] at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1079)
[jbpmschema] at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:354)

Does anyone know why I get this message?

And what is the difference between the 2 build files? do i have to build both files after every change in my code or in my par files?


Thanks in advance

[koen.aers]

Hi Mennen,

The build.deploy.xml file is a convenience build file to create a special jbpm configuration for the jboss application server that will be hosting jbpm. So if you want to use this you have to make sure that the build.properties file contains the proper locations for your jboss installation. The error you get is because the HSQL database could not be started, either because it is already running or because the HSQLDB is not at the expected location, i.e. your jboss home is incorrectly set.

Regards,
Koen

[mennen]

Thank you Koen, now things are getting clearer