Hide Forgot
++ This bug is a clone of bug 779711 ++ Affects: Release Notes project_key: SOA Originally when jbpm.cfg.xml has contained any modifications then configuration in default.jbpm.cfg.xml was disregarded. This behaviour has changed so from maintenance POV it is better to put to jbpm.cfg.xml only changes to default configurations.
Link: Added: This issue related SOA-1998
This has been triaged for SOA 5.1.0. This is not in SOA 5.1.0
The proposed solution for this issue is - Remove all configurations changes from jbpm.cfg.xml that are same as in default.jbpm.cfg.xml - so it contains only changes to default configuration - Document and encourage users to use only jbpm.cfg.xml if they are making any changes into jBPM config
Release Notes Docs Status: Added: Not Required Writer: Added: dlesage
Decision made on Tuesday (March 22nd) that this is now a 'document only' matter.
Release Notes Docs Status: Removed: Not Required Added: Documented as Known Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2075 Red Hat encourages users to make any JBPM configuration changes in the jbpm.cfg.xml file. Originall,y when jbpm.cfg.xml contained any modifications then the configuration found in default.jbpm.cfg.xml was ignored. This behaviour has been changed so that, from a maintenance perspective, it is better to put any changes to the default configuration in jbpm.cfg.xml only.
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2075 Red Hat encourages users to make any JBPM configuration changes in the jbpm.cfg.xml file. Originall,y when jbpm.cfg.xml contained any modifications then the configuration found in default.jbpm.cfg.xml was ignored. This behaviour has been changed so that, from a maintenance perspective, it is better to put any changes to the default configuration in jbpm.cfg.xml only. Added: https://issues.jboss.org/browse/SOA-2075 Red Hat encourages users to make any JBPM configuration changes in the jbpm.cfg.xml file. Originally, when jbpm.cfg.xml contained any modifications then the configuration found in default.jbpm.cfg.xml was ignored. This behaviour has been changed so that, from a maintenance perspective, it is better to put any changes to the default configuration in jbpm.cfg.xml only.
Affects: Added: [Release Notes]
We will not fix this issue, but we need to document it in the release notes (as planned).
Verified in ER2