Bug 793947 (JBEPP-1018)

Summary: WSRP Consumer: consumersConfigLocation is ignored in wsrp-configuration.xml
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Thomas Heute <theute>
Component: unspecifiedAssignee: claprun <claprun>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: epp-bugs, theute
Target Milestone: ---   
Target Release: 5.2.0.ER06   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1018
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-02 18:23:38 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 Thomas Heute 2011-07-20 12:00:59 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
project_key: JBEPP

Comment 1 Thomas Heute 2011-07-20 12:01:12 UTC
Link: Added: This issue is related to GTNPORTAL-1938


Comment 2 Scott Mumford 2011-08-09 04:15:45 UTC
Release Notes Docs Status: Added: Needs More Info
Release Notes Text: Added: If this issue requires a Release Note, more information (about how the problem presented to users and how it was fixed) is required.


Comment 3 Chris Laprun 2011-08-24 13:40:34 UTC
Release Notes Text: Removed: If this issue requires a Release Note, more information (about how the problem presented to users and how it was fixed) is required. Added: The location for the file to use for the consumers configuration specified in the wsrp-configuration.xml was previously ignored. As a result, it was previously impossible to use a different configuration file than the default one. This new version properly honors the location specified in wsrp-configuration.xml by adding the ability to configure consumers from an InputStream similarly to what's being done for the producer configuration. Users should now be able to use their own consumers configuration file instead of having to modify the default one.
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]


Comment 4 Chris Laprun 2011-08-24 13:40:46 UTC
Release Notes Docs Status: Removed: Needs More Info Added: Documented as Resolved Issue


Comment 5 Scott Mumford 2011-08-25 02:48:48 UTC
Release Notes Text: Removed: The location for the file to use for the consumers configuration specified in the wsrp-configuration.xml was previously ignored. As a result, it was previously impossible to use a different configuration file than the default one. This new version properly honors the location specified in wsrp-configuration.xml by adding the ability to configure consumers from an InputStream similarly to what's being done for the producer configuration. Users should now be able to use their own consumers configuration file instead of having to modify the default one. Added: Previous versions of JBoss Enterprise Portal Platform did not honor the location of the WSRP consumer configuration file specified in wsrp-configuration.xml. This made it impossible to use any configuration file other than the default. This version of JBoss Enterprise Portal Platform honors the configuration file location by adding the ability to configure consumers from an InputStream similar to the method used by the producer configuration. Administrators can now use custom consumer configuration files instead of needing to modify the default file.


Comment 6 Chris Laprun 2011-08-26 10:31:21 UTC
Still awaiting confirmation of fix from customer and needs also to be fixed in EPP 5.2.0.CR01.

Comment 7 Scott Mumford 2011-09-19 06:31:08 UTC
This issue was already included in the 5.1.1 Release Notes.
Which is the correct fix version 5.1.1.CR01 or 5.2.0.CR01?

Comment 8 Scott Mumford 2011-09-19 06:31:08 UTC
Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Needs More Info


Comment 9 Thomas Heute 2011-09-20 06:12:11 UTC
It was fixed in both branches, for the release notes, 5.1.1 is enough

Comment 10 Scott Mumford 2011-09-23 00:12:59 UTC
Release Notes Docs Status: Removed: Needs More Info Added: Not Required


Comment 11 Chris Laprun 2011-11-02 18:23:38 UTC
This is fixed but should be properly documented.