Hide Forgot
Date of First Response: 2010-01-20 08:51:53 project_key: SOA Workaround for SOA-1586 is to unsecure the upload servlet (replacing the production console with the dev console). Running 'ant deployProcess' in bpm_orchestration results in this error: [deployToServer] deploying par ... BUILD FAILED /SOA-P-5/er7/jboss-soa-p.5.0.0/jboss-as/samples/quickstarts/bpm_orchestration3/build.xml:62: couldn't deploy process archives : null
If I don't provide username/password it works fine.
To sum it up: I have to leave the jbpm.console.username/pasword blank in jboss-as/samples/quickstart/conf/quickstart.properties and rename the jboss-as/server/production dir, otherwise the producton config is found and the secured URL (/app/upload) is used
This is expected behaviour, the scripts target the configuration of the server as it is shipped. For the full soa server they will use the secured servlet, for the standalone one they will use the unsecured one.
Draft documentation for release notes states: https://jira.jboss.org/jira/browse/SOA-1851 You cannot deploy PAR files via ant when using development's jBPM consoleRunning ant deployProcess in bpm_orchestration results in an error. This is because the scripts target the configuration of the servers that are default when they are shipped. To work around this issue, leave the jbpm.console.username/password in jboss-as/samples/ quickstart/conf/quickstart.properties blank and rename the jboss-as/server/ production directory, so that the producton configuration is not found nor the secured URL (/ app/upload) used.
This is no longer needed, since we don't ship different jbpm consoles (for prod and dev).
Had a look at http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5.0.0/html-single/Release_Notes/#id-release_notes-known_issues and the same note is still listed under https://jira.jboss.org/jira/browse/SOA-1586
This is no longer an issue, since only one console is shipped. Rel notes verified - they don't mention this jira.