Bug 781133 (SOA-3632)

Summary:	Edge case - when user attempts to deploy jBPM project from JBDS to SOA-P server, hypersonic DB artifacts are created
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Len DiMaggio <ldimaggi>
Component:	Tooling, Integration	Assignee:	Marco Rietveld <mrietvel>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.1.0 GA	CC:	smcgowan, tcunning
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-3632
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 SOA-P 5.1 GA
Last Closed:	2012-02-22 11:35:13 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 Len DiMaggio 2011-11-29 17:00:31 UTC

Steps to Reproduce: Configure a SOA_P 5.1 server with JBDS 4 - start the server.
Then create a new jBPM project - and mark it as deployable.
project_key: SOA

The user task is invalid - the correct task is for the user to deploy the PROCESS and not the PROJECT.

But - support for hypersonic has been completely removed from SOA-P - JBDS should have no references/pointers to using it as a default DB for any SOA-related actions.

Comment 1 Len DiMaggio 2011-11-29 17:00:32 UTC

Link: Added: This issue Cloned from SOA-3060

Comment 2 Marco Rietveld 2012-02-22 11:35:13 UTC

I'm closing this for a number of reason: 

1. This is an edge case and no customer has complained about this. 
2. The original bug was never verified. Please see 
   - https://issues.jboss.org/browse/JBDS-1650