[
http://jira.jboss.com/jira/browse/JBPM-1117?page=all ]
Tom Baeyens updated JBPM-1117:
------------------------------
Fix Version/s: (was: jBPM 3.2.2 SOA 1)
This is what I get from this discussion:
* You can use the ant deploy target, providing it with a configuration file that points to
a jBPM DB.
* The jBPM Console also contains a config file pointing to the jBPM DB.
* So if you update one of those configuration files without the other then the deployed
process is not seen in the console.
Would the following be a solution ?
* Make sure that a jBPM installation always has a deployment servlet
* That way, the ant task and the designer can both deploy to a URL
* So there is only 1 configuration of the database. And the ant task and the designer
only need to be configured with a URL
We'll take this into account in building jPDL 4. I don't think we can still
prioritize this for jBPM 3.
ProcessDefinition deployment to a running server using ant, and the
servlet.
----------------------------------------------------------------------------
Key: JBPM-1117
URL:
http://jira.jboss.com/jira/browse/JBPM-1117
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Reporter: Kurt Stam
Assigned To: Tom Baeyens
Attachments: DeployProcessToServerTask.java
When using in-memory databases it is hard to deploy processdefinitions using the current
'DeployProcessTask'. Instead would like to deploy to the servlet (like the IDE
does).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira