Search:

Using codes as follows instead of new ProcessDefinition, it's ok.


ProcessDefinition definition = ProcessDefinition.createNewProcessDefinition();

I agree with you in hibernate message.

Now I think that the problem in defining jbpm process with jbpm's api.

What I missed?

Any idea? Thanks in advance.

It runs successfully with process:
ProcessDefinition processDefinition = ProcessDefinition
.parseXmlString("<process-definition name='howareyou'>"
+ " <start-state name='start'>"...

After change a process definition, it 's ok.

2. jbpm.cfg.xml
<jbpm-configuration>

<!--
The default configurations can be found in org/jbpm/default.jbpm.cfg.xml
Those configurations can be overwritten by putting this file...

configuration:

1. hibernate.cfg.xml
<?xml version='1.0' encoding='utf-8'?>

<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
...

I can deploy new process successfuly, but when I want to store variables in ContextInstance, it failed.

code snippet:
this.jbpmTemplate.execute(new JbpmCallback(){

/**
*...