Is this trick still required? I thought that we implement
now the destroy() method of the servlet, so everything should
be cleaned up fine.

If not, could you please add this to the faq?


Carsten

Open Source Group                        sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de                          mailto: [EMAIL PROTECTED]
================================================================


> -----Ursprüngliche Nachricht-----
> Von: Sylvain Wallez [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 19. Juli 2001 09:58
> An: [EMAIL PROTECTED]
> Betreff: Re: [C2]: Testing for beta2
>
>
>
>
> giacomo a écrit :
> >
> > On Wed, 18 Jul 2001, Donald Ball wrote:
> >
> > > On Wed, 18 Jul 2001, Vadim Gritsenko wrote:
> > >
> > > > Don't blame on SQL examples, they are working - just set
> <dburl>! ;-)
> > > >
> > > > Donald,
> > > > what is your (non-working) configuration?
> > >
> > > just dropping the cocoon.war file into resin or tomcat. i
> thought that the
> > > default cocoon.war file was supposed to fire up an hsqldb
> instance with
> > > the tables already created and such. not so? if not, then why are we
> > > including hsqldb??
> >
> > The sql samples are working when deploing the war file using the build
> > system:
> >
> >   ./build.sh \
> >     -Dinclude.webapp.libs=yes \
> >     -Dinstall.war=path/to/tomcat/webapps
> >     install
> >
> > This command will take care the path inside the configuration file to
> > the hsqldb resources.
> >
> > Giacomo
> >
> Also, if the servlet engine is stopped abruptly (e.g. ctrl-C), the db
> isn't closed properly and requires manual unlocking. See
> http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=99191289428482&w=2
> for the trick.
> --
> Sylvain Wallez
> Anyware Technologies - http://www.anyware-tech.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to