[
https://jira.jboss.org/jira/browse/GTNPORTAL-699?page=com.atlassian.jira....
]
Matt Wringe commented on GTNPORTAL-699:
---------------------------------------
The changes set in the first comment are correct, but its not working because of the
sample portal extension.
The change is not set in the sample portal extension, so the extension set its as the
default (classic), then the extension overwrites the value specified in the normal
portal.
We should have it setup so that if the extension doesn't specify a value then the
value is taken from the portal itself. And since we can't run the portal without the
extension properly right now, its a bit of a pain.
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