Bug 793657 (JBEPP-735)

Summary: Move jgroups stack configuration out of exo.portal.component.common-<version>.jar
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Martin Weiler <mweiler>
Component: Portal, Portal PackagingAssignee: hfnukal <hfnukal>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.CR01, 5.1.1.DEV01CC: epp-bugs, hfnukal, mposolda, mweiler, theute
Target Milestone: ---   
Target Release: 5.1.1.DEV02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-735
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-21 08:19:15 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 793658, 793688, 793696    
Bug Blocks:    

Description Martin Weiler 2010-12-15 13:57:15 UTC
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000004UaFc
project_key: JBEPP

Currently the jgroups configuration file is packaged inside gatein.ear/lib/exo.portal.component.common-<version>.jar, which makes it hard to change the jgroups stack. Should be moved to a location within gatein.ear where it can be edited directly.

Comment 1 Thomas Heute 2010-12-15 14:14:59 UTC
Which jgroups configuration files ? (there are multiple ones for multiple channels) ?
In general, you can define where to pickup the configuration file, so that you can always leave the one that we package intact in its jar and just specify a new location for a custom one.

Comment 3 hfnukal@redhat.com 2011-03-29 10:19:36 UTC
Link: Added: This issue depends JBEPP-736


Comment 4 hfnukal@redhat.com 2011-03-29 10:19:36 UTC
Link: Added: This issue depends JBEPP-764


Comment 5 hfnukal@redhat.com 2011-03-29 10:19:37 UTC
Link: Added: This issue depends JBEPP-772


Comment 6 hfnukal@redhat.com 2011-03-29 10:25:18 UTC
I  close this issue as it is linked to other issues
and I set Fix version 5.1.1.GA

Comment 7 Thomas Heute 2011-04-13 07:39:45 UTC
Would be better to not close them until the dependent or related ones are not closed.
Here it seems like the feature describe by the JIRA is fixed but it is not.

Comment 8 hfnukal@redhat.com 2011-04-14 14:03:24 UTC
Release Notes Docs Status: Added: Needs More Info


Comment 9 Scott Mumford 2011-04-29 03:00:06 UTC
Release Notes Docs Status: Removed: Needs More Info Added: Not Required


Comment 10 mposolda 2011-05-06 12:44:19 UTC
I am reopening, since not all JBC configurations are removed from JAR file.

Only JBoss cache configuration, which is used for MOPSessionManager, has been moved from location /component/common/src/main/java/conf/jbosscache .

But JBoss cache and JGroups configuration, which is used for JCR, is still in old location /component/common/src/main/java/conf/jcr/ , which is in final EPP build inside JAR file $EPP_HOME/server/production/deploy/gatein.ear/lib/exo.portal.component.common-5.1.1-epp-DEV01.jar#conf/jcr

Comment 11 mposolda 2011-10-26 08:53:11 UTC
Link: Added: This issue is related to GTNPORTAL-2234