This error happens when using the derby database with description or delegation in your process definition that are longer that 255 characters long. It comes from a bug in the DerbyDialect of hibernate that creates column of length 255 instead of ... much longer. You have 2 ways of fixing the problem, either using a fixed DerbyDialect or modifying the database once it is created.
- Using a fixed DerbyDialect
Nuxeo´s jBPM service comes with DefaultClobDerbyDialect, that creates default length clob (2M) instead of 255 characters. To use it add this line to your hibernate configuration file, the one referenced in the jbpm configuration file:
You can, for example create a bundle with the following jbpm-service-contrib.xml :
Add a config/derby.jbpm.cfg.xml file with the following contents :
And add a config/derby-jbpm-hibernate.cfg.xml file copied from the one of the nuxeo-platform-jbpm-core bundle just adding the dialect class specification :
Then, the only thing to be sure of is that the bundle where the process definition lies requires the configuration bundle just created (so that it is deployed after the configuration bundle).
- Modifying the database
The default configuration is to set <code>hbm2ddl.auto</code> to update, that is, if hibernate finds a modification then it modifies the database. So when you start the server for the first time, or when you deleted your data, all the tables are created. You can start the server and login. The tables are created. Shutdown the server and use a tool from derby to access and modify the database.
The Derby website has tools to connect and run script against the database. You can find the database in:
The script to run is: