| Summary: | jbpm.cfg.xml in jbpm.esb has to be cleaned-up to contain onfly differences to default.jbpm.cfg.xml | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | JBPM - within SOA | Assignee: | Len DiMaggio <ldimaggi> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 GA | CC: | jpechane, ldimaggi, nwallace |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2075 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | SOA-2075 | Environment: | |
| Last Closed: | 2011-04-20 13:02:01 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
Jiri Pechanec
2010-05-07 09:46:51 UTC
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 |