I believe that is correct. When you shutdown it writes the xreg files out to disk,
however:
the following may also be true:
User starts Jetspeed.
User makes changes to xreg files
Registry runs is filewatcher, sees the change, and loads the changes.
If the server is shutdown at this point it may write the changes back to the file
system. I have not verified this however.
Check the Registry service entry in JR.props.
#########################################
# Registry Service #
#########################################
services.Registry.classname=org.apache.jetspeed.services.registry.CastorRegistryService
services.Registry.directory=/WEB-INF/conf/novus/
services.Registry.mapping=/WEB-INF/conf/novus/registry.xml
services.Registry.default.Portlet=local-portlets
services.Registry.default.PortletControl=local-managers
services.Registry.default.PortletController=local-managers
services.Registry.default.MediaType=local-medias
services.Registry.default.Skin=local-skins
services.Registry.default.Security=local-security
services.Registry.extension=.xreg
# Refresh rate, in seconds. 0 = no refresh. Min value = 60
services.Registry.refreshRate=1000000
Also if you are interested in some code to view the Registry here is a code snippet
Enumeration registryEntrys =
org.apache.jetspeed.services.Registry.getNames();
while (registryEntrys.hasMoreElements())
{
String regEntry = (String)registryEntrys.nextElement();
System.out.print(regEntry);
Registry reg =
org.apache.jetspeed.services.Registry.get(regEntry);
System.out.println(" : " + reg.toString());
RegistryEntry entry[] = reg.toArray();
for (int i = 0; i < entry.length; i++)
{
RegistryEntry registryEntry = entry[i];
System.out.println("\t" + registryEntry.getName());
}
}
-----Original Message-----
From: Ray O'Donnell [mailto:ray.odonnell@;norkom.com]
Sent: Friday, October 18, 2002 6:09 AM
To: 'Jetspeed Users List'
Subject: RE: configuration files (xreg) destroyed after shutdown
Hi
I also have been trying to understand how the xregs work.
If I understand correctly, Jetspeed has a filewatcher process sitting on top
of the xregs, so that for example if I add a new portlet, the filewatcher
would detect the change and load the new portlet. This is great because it
means that I can tweak the xregs without having to restart Jetspeed.
However Jetspeed also flushes the xregs from memory to disk on shutdown, and
without invoking filewatcher first. This means that any manual changes I
made since the last time filewatcher loaded the file will get clobbered.
Can anyone tell me if this is correct?
Ray
-----Original Message-----
From: Tegethoff, Jan [mailto:JTegethoff@;koeln.sema.slb.com]
Sent: 16 October 2002 15:44
To: 'Jetspeed Users List'
Subject: AW: configuration files (xreg) destroyed after shutdown
Thanks for your quick answer!
How exactly do you do this? I usually shut down tomcat using the
automatically provided menu-item which does this by calling
java.exe -jar -Duser.dir="C:\Programme\Apache Group\Tomcat 4.1.12"
"C:\Programme\Apache Group\Tomcat 4.1.12\bin\bootstrap.jar" stop
I see the possibility of each time stopping jetspeed using the tomcat
management application prior to stopping tomcat itself. Is that what you
suggest?
Jan
-----Urspr�ngliche Nachricht-----
Von: Werner Punz [mailto:werpu@;gmx.at]
Gesendet: Mittwoch, 16. Oktober 2002 16:37
An: Jetspeed Users List
Betreff: Re: configuration files (xreg) destroyed after shutdown
Hello I know the problem, but it�s not that bad actually. What happens?
When you start a shutdown process the xregs are written onto the config
directory as it seems. Well if you kill the shutting down process some
of the xregs aren�t written properly and left empty.
The solution at least in my case was not to kill tomcat during the
shutdown process but giving it enough time to shut down propery and
kill itself after everything ist done. At least that did the trick to me
on Tomcat 4.1
Werner Punz
--
Labor-C GesmbH
http://www.labor-c.net
Tegethoff, Jan wrote:
> Hi all!
>
> I have a problem running Jetspeed which has been stated before on this
> mailing list - however the answers don�t really help me.
> Whenever Tomcat gets shut down, some .xreg-files in the conf-directory are
> cut short to 1k, leaving only a few tags (definetly no well-formed xml).
In
> this way the Jetspeed-installation gets destroyed every time. There has
been
> a suggestion on this mailing-list that castor rewrites all these files
when
> tomcat gets shut down, but knowing this doesn�t really help me.
>
> I am using the following software:
> JDK1.4.0_01
> Tomcat 4.0.4 or 4.1.12 (I tried both with the same result)
> Jetspeed 1.4b1 ('out of the box' i.e. without any further alterations or
> configurations)
>
> Another problem is that using jetspeed the tomcat process sometimes gets
> killed without further notice or obvious cause. This may or may not be
> connected to the first problem.
>
> Any suggestion would be greatly appreciated!
> Jan
>
--
To unsubscribe, e-mail:
<mailto:jetspeed-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:jetspeed-user-help@;jakarta.apache.org>
The information contained in this e-mail transmission is confidential
and may be privileged. It is intended only for the addressee(s) stated
above. If you are not an addressee, any use, dissemination, distribution,
publication, or copying of the information contained in this e-mail is
strictly prohibited. If you have received this e-mail in error, please
immediately notify our IT Department by telephone at 353-1-6769333
or e-mail [EMAIL PROTECTED] and delete the e-mail from your
system.
--
To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
