[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Jiri Peterka commented on JBIDE-7347:
-------------------------------------
Koen, now it's clear what has happened. Issue is here when "gpd-deployer"
instead of "gpd-deployer/upload" is set as server deployer. jBPM tools somehow
thinks everything is all-right and reports successful deployment although is not true.
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL:
https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira