[
https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin....
]
Koen Aers commented on JBDS-1650:
---------------------------------
But AFAICS this is not at all jBPM related then. If you would create a random project in
JBDS with a HSQLDB config in it and you mark it deployable and try to deploy it to the
SOA-P server than the same thing would happen, right? Anyway, I suspect that this
behaviour would not occur if you remove the jbpm-hsqldb-ds.xml file from the
'config' folder in the jbpm project. Can you verify if that is the case? If it is,
the issue can be solved by not including this file in the jBPM runtime that is shipped
with SOA-P.
Edge case - when user attempts to deploy jBPM project from JBDS to
SOA-P server, hypersonic DB artifacts are created
--------------------------------------------------------------------------------------------------------------------
Key: JBDS-1650
URL:
https://issues.jboss.org/browse/JBDS-1650
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: jBPM, SOA Platform
Affects Versions: 4.0.0.GA
Environment: Version: 4.0.0.GA
Build id: v20110216-1930-H239-GA
Build date: 20110216-1930
SOA-P 5.1 GA
Reporter: Len DiMaggio
Assignee: Koen Aers
Priority: Minor
Fix For: 4.1.0.CR1
See: SOA-3060
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira