jbpm-bpel-1.0-alpha3 Problems

[aguizar]

Robert,

The only way you would not need to change the database configuration as pointed out in section 2.4.1 is having this exact environment:
- a local MySQL server listening to the default port (3306)
- a database named "jbpm"
- an user named "jbpm_user" with all privileges on the "jbpm" database identified by password "hopesystems"

Further, you need to put the JDBC driver for MySQL in the server classpath.

The user guide intentionally omitted DBMS, database and user setup as that is out of the scope of the project.

[robert27329]

Alex-

Thanks for the explanation concerning the DBMS usage as it is currently setup, I thought that Boss 4.0.2 already ships with a persistance layer DBMS and that the alpha 3 version of BPEL would require no additions/changes to work with it.

Is the database issue the cause of this error reported by the JBoss server about not being able to read the file "org/jbpm/bpel/exe/LinkInstance.hbm.xml"?

2005-09-13 09:09:01,325 ERROR [org.jbpm.db.jmx.JbpmService] Starting failed jboss.jbpm:name=DefaultJbpm,service=JbpmService
org.hibernate.MappingException: Error reading resource: org/jbpm/bpel/exe/LinkInstance.hbm.xml

I have installed MySQL and will attempt to setup the default environment as you have specified.

When you say, "put the JDBC driver for MySQL in the server class path." do you mean copy it to "%JBOSS_HOME%\server\default\lib"?

Some mention of what DBMS parts are required for the default setup would be helpfull in the getting started document for people like my self who are unfamiliar with this product and JBoss in general. I did go to and read the references in the configuration section but still did not understand that additional software was needed in order to deploy the jbpm-bpel.sar file.

Thanks for your help,
Robert

[robert27329]

Alex-

One solution to this problem that a co-worker found is to remove and reinstall the JBoss server. Once that was done, and MySQL server installed with the appropriate settings I was able to complete the "HelloWorld" example without any problems.

I had been using the existing JBoss server installation with the alpha2 version of the BPEL extension, however I would not know why that would cause the problem I was seeing.

Thanks,
Robert

[aguizar]

Robert,

Thanks for finding and sharing a solution. I once found a similar problem during a debug session of alpha 3, but it was because I was deploying the service archive without rebuilding it. Could it be that the service archive from alpha 2 was left behind? In any case, do you know how to reproduce the problem?

JBoss already ships with a persistence layer DBMS

-> Good point. I'll try to use the default data source to facilitate testing in future releases.

Some mention of what DBMS are required for the default setup would be helpful in the getting started document

-> I will extend the documentation on database setup, too.

[robert27329]

Alex-

Could it be that the service archive from alpha 2 was left behind? In any case, do you know how to reproduce the problem?

No, I am not familiar enough with JBoss to debug/reproduce the problem, I did save the JBoss directory and files and could send them to you via email if you want that do show the problem.

Thanks again,
Robert