[
https://issues.jboss.org/browse/JBIDE-8228?page=com.atlassian.jira.plugin...
]
Koen Aers commented on JBIDE-8228:
----------------------------------
The "/jbpm-console/upload" value is used for community release jBPM runtimes
(such as jBPM 3.1.x) as the servlet is unprotected in those releases; the
"gpd-deployer/upload" value is used for product release jBPM runtimes (such as
SOA-P) as the servlet is password protected for those releases.
AFAIK JBDS uses the "/gpd-deployer/upload" value as a preference, JBT uses
"/jbpm-console/upload". This is how it was meant to be. These preferences are
changeable on the appropriate preference page.
So I guess the real question is: are there any users that use the JBT/SOA-P combination,
or do most/all of the JBT users use community jBPM releases?
It is anyhow a pretty trivial change if it would be needed.
Default jBPM Server Deployer set to gpd-deployer/upload
-------------------------------------------------------
Key: JBIDE-8228
URL:
https://issues.jboss.org/browse/JBIDE-8228
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jbpm
Affects Versions: 3.2.0.CR1
Environment: JBT 3.2.CR1, Linux 64
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.2.1, 3.2.0.CR2 (tentative)
Currently default server deployer (jBPM Process -> Deployment Page -> Server
Deployer) is set to /jbpm-console/upload. For recent JBoss runtimes (SOA-P specifically)
default jBPM deployer is "gpd-deployer/upload". If there are no other reasons
for keeping the old value, I suggest to change it to "gpd-deployer/upload".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira