project_key: SOA Related to https://issues.jboss.org/browse/SOA-2937 The enterprise is using "/gpd-deployer/upload" and the community is using "/jbpm-console/upload". For JBDS, we should have the default value be "/gpd-deployer/upload" - as this is what the SOA Platform requires.
Link: Added: This issue is related to SOA-2937
Link: Added: This issue is a dependency of JBDS-1645
Link: Added: This issue relates to JBDS-1646
Looks like this was only a JBDS issue and doesn't have to do with jBPM. All yours, Julian! :)
Based on the last comment to JBDS-1645, this appears to have been resolved in the upcoming JBDS 4.1 release.
Link: Added: This issue Cloned to SOA-3630
The associated JIRAs are closed; I guess we should verify this in 5.0.0.CR1.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: There was an incorrect jBPM upload URL in previous versions. The URL originally reffererd to "/jbpm-console/upload" but it should have been "/gpd-deployer/upload". This problem has been fixed so "/gpd-deployer/upload" appears as the default value.
Verified on SOA 5.3 ER5 and JBDS 5.0.0.GA + JBT SOA-Tooling 3.3.0.v20120620-0445-H5-CR1-SOA. Window -> Preferences -> JBoss jBPM -> jBPM 3 -> Server Deployment has server deployer set to /gpd-deployer/upload.
Can we close this?