Hide Forgot
Date of First Response: 2007-11-07 14:06:04 project_key: SOA There is hard coded datasource configuration for SchemaDeployer in server/*/lib/jboss-soa-schema-deployment.jar:jbpm-deployment.properties (JbpmDS) and no support for other databases than HSQLDB. But in server/*/deploy/soa-jbpm-deployment-service.xml where the service MBean is configured the correct datasource is referenced. There was a discussion about removing this service at all. It should be either 1) configured in the deploy or conf directory (not in lib) or 2) removed
This isn't quite an accurate assessment of what's there. The datasource is, in fact, not hard coded. The jbpm-deployment.properties is a deployment script mapping file, which currently only has DDL mapped for HSQLDB. For example, if you reconfigure the datasource to something other than HSQLDB, it will simply not perform an auto-deploy without a compatible scirpt to run.
I don't consider a /lib/ directory as a good place for configuration files. If the file is 1) in /lib/ directory 2) packed in a jar library then it is definitely hard coded, because customer won't definitely expect it. I think we should 1) add DDLs for other databases (do you want me to create a JIRA task for it?) 2) I want to reconfigure datasource NAME to something different than JbpmDS
ad 2) the customer must be able to change the datasource name to something different than JbpmDS
This component is deprecated/removed.
Verified for IR6