Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1066495 - Portal Container Paths in Configuration Retrieval section
Summary: Portal Container Paths in Configuration Retrieval section
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Documentation
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: JPP Docs Team
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-18 14:25 UTC by Aakanksha
Modified: 2018-10-17 21:29 UTC (History)
6 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 22538, Development Guide-6.1-6.1.1 Build Date: 05-02-2014 21:49:56 Topic ID: 18935-581027 [Latest]
Last Closed:
Type: ---


Attachments (Terms of Use)

Description Aakanksha 2014-02-18 14:25:58 UTC
Selected Text: "Services default PortalContainer configurations from JAR files $JPP_HOME/conf/portal/configuration.xml"

Bug Details: 

Comments from Thomas (theute@redhat.com) and Thomas (tkyjovsk@redhat.com)

>  these are configurations from JAR files, so the path is supposed to be relative to the root folder of the particular JAR file (so no $JPP_HOME here)
+1
> --- FYI: in this case these are JAR files of various portal modules, which are located in $JPP_HOME/modules/system/layers/gatein further under the /org/gatein subfolder (someone from the dev team should validate this info, as I'm not 100 % sure about it)
I think it's any jar in the classloader

Comment 1 Jared MORGAN 2014-05-27 04:48:50 UTC
This work relates to http://docbuilder.usersys.redhat.com/22538/remarks/#Configuration_Retrieval

Update:

>  these are configurations from JAR files, so the path is supposed to be relative to the root folder of the particular JAR file (so no $JPP_HOME here)
+1

I have removed the JPP_HOME notations from the first three items in the list as I assume that is what the first comment about the root folder of the app was relating to.

I have left the JPP_HOME notations for the sub-bullets because I believe when RHJP can't find the config in the webapp, it looks up the tree into the portal for default config.

> --- FYI: in this case these are JAR files of various portal modules, which are located in $JPP_HOME/modules/system/layers/gatein further under the /org/gatein subfolder (someone from the dev team should validate this info, as I'm not 100 % sure about it)

Not sure what this relates to. Will leave this for you to address, Aakanksha.

Comment 4 Tomas Kyjovsky 2014-10-07 13:00:18 UTC
Aakanksha, I reviewed the section "⁠A.3. Configuration Retrieval".

As for the: "NEEDINFO - potentially unsupported code fragment here because it refers to exo-tomcat which would be tomcat container and therefore not supported by Red Hat. What would be replacement code? I've commented it out because it doesn't seem valid"

I assume this refers to the code snippet above:

"java -Dorg.exoplatform.container.configuration.debug ..."

I performed a quick test on 6.2.0.CR2 and it works fine.


Regarding the bulletpoints: In the original exo doc I can see 2 separate sections: one for PortalContainer, one for StandaloneContainer, however in our docs they are merged into one and I'm not sure this is entirely correct. I will consult someone from the dev team and comment with a suggestion.


Note You need to log in before you can comment on or make changes to this bug.