Hide Forgot
Date of First Response: 2008-06-23 23:01:42 project_key: SOA The affect of JBESB-1673 on running quickstarts on the embedded server/production configuration is that users will have to: 1) Create a jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/quickstarts.properties file (an example file is included in the same dir) 2) Define these values in quickstarts.properties - and provide the correct username and password (e.g., "admin") jbpm.console.username= jbpm.console.password=
Link: Added: This issue depends JBESB-1673
This is new for CP02 - as the fix for JBESB-1673 is also new for CP02.
Release noted: 8.1. Running Quickstarts with JBPM Quickstarts which use JBPM need to authenticate to the jbpm console when they are run in the protected production environment. Here are the steps to do this. Procedure 5. Authenticating Quickstarts to the JBPM Console 1. Create a jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/quickstarts.properties file. 2. Define the following values in quickstarts.properties - and provide the correct username and password (e.g. "admin"). jbpm.console.username= jbpm.console.password= Further information: http://jira.jboss.com/jira/browse/SOA-579
Josh - all the quickstarts need this in the production config - not just jBPM...
Len, the change is only relevant to the jBPM upload servlet. Why does this affect the other quickstarts?
Because the check is done in cons/base-build.xml for all quickstarts
Then the check is wrong and needs to be fixed. It should only have affected the jBPM quickstarts.
JBESB-1847 covers the ESB aspect
Link: Added: This issue related JBESB-1847
Verified resolved in the CP02 CR4 release notes.