Bug 781133 (SOA-3632) - Edge case - when user attempts to deploy jBPM project from JBDS to SOA-P server, hypersonic DB artifacts are created
Summary: Edge case - when user attempts to deploy jBPM project from JBDS to SOA-P serv...
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-3632
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling, Integration
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: FUTURE
Assignee: Marco Rietveld
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 17:00 UTC by Len DiMaggio
Modified: 2016-09-20 05:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780622 0 medium CLOSED Edge case - when user attempts to deploy jBPM project from JBDS to SOA-P server, hypersonic DB artifacts are created 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-3632 0 None Closed Edge case - when user attempts to deploy jBPM project from JBDS to SOA-P server, hypersonic DB artifacts are created 2012-03-07 21:54:49 UTC

Internal Links: 780622

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
Note You need to log in before you can comment on or make changes to this bug.