Bug 779466 (SOA-1851)

Summary: par files canot be deployed via ant task when using dev's jBPM console
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: Documentation, ExamplesAssignee: Jaroslaw Kijanowski <kijanowski>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER7   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1851
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-22 07:57:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jaroslaw Kijanowski 2010-01-20 12:48:48 UTC
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

Comment 1 Jaroslaw Kijanowski 2010-01-20 12:57:12 UTC
If I don't provide username/password it works fine.

Comment 2 Jaroslaw Kijanowski 2010-01-20 13:03:45 UTC
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

Comment 3 Kevin Conner 2010-01-20 13:51:53 UTC
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.

Comment 4 David Le Sage 2010-02-09 01:30:46 UTC
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.


Comment 5 Jaroslaw Kijanowski 2010-02-10 11:59:30 UTC
This is no longer needed, since we don't ship different jbpm consoles (for prod and dev).

Comment 7 Jaroslaw Kijanowski 2010-02-22 07:57:29 UTC
This is no longer an issue, since only one console is shipped.
Rel notes verified - they don't mention this jira.