Bug 777592 (SOA-100)

Summary: SOA jBPM deployment service configuration problems
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Martin Vecera <mvecera>
Component: JBossESBAssignee: Mike Brock <cbrock>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR4CC: rruss
Target Milestone: ---   
Target Release: 4.2 IR6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-100
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-19 14:57:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Vecera 2007-11-06 09:37:11 UTC 
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
Comment 1 Mike Brock 2007-11-07 19:06:04 UTC 
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.
Comment 2 Martin Vecera 2007-11-08 08:57:39 UTC 
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
Comment 3 Martin Vecera 2007-11-08 15:35:53 UTC 
ad 2) the customer must be able to change the datasource name to something different than JbpmDS
Comment 4 Mike Brock 2007-11-15 00:41:36 UTC 
This component is deprecated/removed.
Comment 5 Martin Vecera 2007-11-19 14:57:38 UTC 
Verified for IR6