Hide Forgot
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.
Link: Added: This issue is a dependency of JBDS-1650
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.
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!
Link: Added: This issue Cloned to SOA-3632
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