Bug 780622 (SOA-3060) - 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-3060
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Tooling, Integration
Version: 4.3 CP05
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-05-05 18:58 UTC by Len DiMaggio
Modified: 2016-09-20 05:04 UTC (History)
1 user (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:05 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781133 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-3060 0 None Closed Edge case - when user attempts to deploy jBPM project from JBDS to SOA-P server, hypersonic DB artifacts are created 2012-02-22 11:35:11 UTC

Internal Links: 781133

Description Len DiMaggio 2011-05-05 18:58:37 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-05-05 19:01:38 UTC
Link: Added: This issue is a dependency of JBDS-1650


Comment 2 David Le Sage 2011-05-26 22:14:44 UTC
Release Notes Docs Status: Added: Documented as Known Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/JBDS-1650

If the user attempts to deploy a jBPM project from JBDS to the SOA Platform server, Hypersonic database artifacts are created. This results in an invalid class as Hypersonic is no longer supported.  The user should deploy the process, not the project.


Comment 3 (please assign to mrietvel@redhat.com) 2011-07-25 08:37:13 UTC
Len, 

When you get a chance, please see JBDS-1650: it _seems_ like this issue is no longer pertinent given that Koen was not able to reproduce the problem. 

If you're still seeing the problem, I don't mind looking into it -- but I'd like to confirm first that it's still a problem. 

Thanks!

Comment 4 Len DiMaggio 2011-11-29 17:00:32 UTC
Link: Added: This issue Cloned to SOA-3632


Comment 5 Marco Rietveld 2012-02-22 11:35:05 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.