> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Andrew Savory > Sent: woensdag 14 november 2007 15:58 > To: Hippo CMS development public mailinglist > Subject: Re: [HippoCMS-dev] A bunch of feedback > > Hi, > > On 11/14/07, Bartosz Oudekerk <[EMAIL PROTECTED]> wrote: > > > > Andrew Savory wrote: > > > Hi, > > > > > > On 11/14/07, Jeroen Reijn <[EMAIL PROTECTED]> wrote: > > >> Try to start it the other way around and see what happens: > > >> > > >> First the CMS and then start up the repository. > > > > > > > > > That seems to work fine. I automatically start the > repository first, > > > so > > I > > > never spotted it :-( > > > > > > Seems this is a problem though, since the CMS and repo > are supposed > > > to > > be > > > started and stopped independently... > > > > Not really, both sites and repositories won't initialise > properly if > > the repository is not running, although they will survive a > repository > > being restarted or otherwise temporarily unavailable after > they've started. > > > > Just as you need to have a database running before you start the > > repository, you need to have the repository running before > you start a > > hippo-cocoon application. > > > > IMHO this is normal (expectable) behaviour..... > > > No, it's not ;-) > > It makes no sense that the CMS only works if it's started > _BEFORE_ the repository ... which provides data necessary for > it to operate correctly. > This is a new bug (possibly a Mac OS X problem), since it's > never happened this way before ... > Strange. I had everything running in Leopard (with JDK 1.5) both from the binary distributions and by building the latest trunks. I started the repository first and then the CMS. No extensions or whatsoever. I only got the wrapper warning about not being able to access the wrapper file. I haven't tried it with Java4 on my Leopard.
Jasha ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
