[gatein-issues] [JBoss JIRA] Resolved: (GTNPORTAL-699) problem with setting up default portal
[
https://jira.jboss.org/jira/browse/GTNPORTAL-699?page=com.atlassian.jira....
]
Matt Wringe resolved GTNPORTAL-699.
-----------------------------------
Resolution: Done
A fix has been committed into svn that will fix this issue (revision 1826).
It checks if the extension is setting the default portal name or it its using the default.
Its its using the default then it wont overwrite the one set by portal. If the extension
does set the portal name, then it will overwrite the one set by the portal.
More investigation may be needed to see what else extensions are overwriting with
defaults.
problem with setting up default portal
--------------------------------------
Key: GTNPORTAL-699
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-699
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-CR01
Reporter: Prabhat Jha
Fix For: 3.0.0-GA
Original Estimate: 4 hours
Remaining Estimate: 4 hours
As reported by Michal:
today I tried to run qVue on GateIn CR1 and everything works fine. Just one thing
doesn't work correctly and it is a configuration of default portal in
gatein.ear/02portal.war/WEB-INF/conf/portal/portal-configuration.xml :
<init-params>
<value-param>
<name>default.portal</name>
<description>The default portal for checking db is empty or
not</description>
<value>qVuePortal</value>
</value-param>
When I start start GateIn, I always have classic portal as default.
I also tried to create new portal in UI and then set this portal name in this property
and doesn't work as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira