Maybe some change in cocoon 2.2 ??? or eXist...
Will post that in eXist, see if I get anything
Thanks
--- Kai Mütz <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED]
> <> wrote:
> > Tried that. Still get the problem.
> > Servlet startup in my web.xml are as follow (and
> in
> > that order):
> > 1) lo
[EMAIL PROTECTED] <> wrote:
> Tried that. Still get the problem.
> Servlet startup in my web.xml are as follow (and in
> that order):
> 1) log4j
> 2) EXistServlet
> 3) DatabaseAdminServlet
> 4) cocoon
>
>
I have the same configuration running without problems on debian linux with
cocoon 2.1.8 and
Tried that. Still get the problem.
Servlet startup in my web.xml are as follow (and in
that order):
1) log4j
2) EXistServlet
3) DatabaseAdminServlet
4) cocoon
--- Kai Mütz <[EMAIL PROTECTED]> wrote:
> Try to start eXist during application startup by
> declaring the
> DatabaseAdminServlet in web.
Try to start eXist during application startup by declaring the
DatabaseAdminServlet in web.xml and starting in before Cocoon servlet, e.g.:
DatabaseAdminServlet
org.exist.http.servlets.DatabaseAdminServlet
configuration
conf.xml
basedir
WEB-INF/
Hi all,
My application uses cocoon 2.2 and an embedded eXist
database. The eXist part runs well on my developpement
environement (XP, jetty) but I run into problems
deploying it on my production server (Linux, tomcat
5.5.9).
After (re)starting the webapp, I connect to my base
URL and get the "Loca
