On Sat, Jul 12, 2008 at 21:28, Kito D. Mann <kmann@xxxxxxxxxx> wrote:
Hello,
While customizing eXo, I've run into a few questions:
· Is it possible to change the default portal
name from classic to something else?
Yes. But it requires some work. In short, in
portal-configuration.xml change
<value-param>
<name>default.portal</name>
<description>The default portal for checking db is empty or not</description>
<value>classic</value>
</value-param>
Then update occurences of 'classic' in files that are under :
WEB-INF/conf/portal
Does that work after the database has already been populated?
· Does hot deployment work? Restarting a
portlet app seems to cause an exception in eXo.
Hot deployment of eXo himself doesn't work. But hot
deployment of a portlet should work.
Ok. I’ve been having some problems with that, so I’ll
let you know if I get a specific stack trace or error. It could just be Tomcat’s
fault.
- The startup is very slow;
is there any way to speed it up (perhaps disabling non-essential services,
like the FTP service)? (I'm using the I'm using the portal + ECM bundle).
How slow? First startup on an empty database or any startup?
Any startup. It takes about a minute, I think. Granted,
this is with several additional portlets and MySQL running on the same machine.
But I still think it might be a bit slow.
-
- There are some nodes that
I'd like to be hidden from navigation. I can do this by modifying the
UIPortalNavigation template. but is there a better way to hide a node from
navigation (perhaps using the enabled property, or by adding a visible
property)?
Ok. I voted for it and added a comment :-).
--
Patrice Lamarque
eXo Platform SAS
