More or less :-) It was meant in the sense that the Cocoon Xalan version is not used, but JDK version. Though it works in most cases (e.g. using JDK's 2.2.D11 instead of Cocoon 2.0.4's 2.3.1), it sometimes crashes. The environment check would clarify it. And of course it was only a guess.

Joerg

Geoff Howard wrote:
Really?  I don't recognize that error as the typical endorsed lib
problem, and thought Jetty handled endorsed libs differently and
so didn't suffer this problem.  Gabriel, did this work?

Geoff


-----Original Message-----
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]

Hello Gabriel,

you seem to have the infamous endorsed libs problem. Try the environment
check mentioned at
http://wiki.cocoondev.org/Wiki.jsp?page=NoMoreDtmIdError to be sure.
Also a short overview about solutions is given. A more complete
description of the problem can be found at
http://wiki.cocoondev.org/Wiki.jsp?page=EndorsedLibsProblem.

Joerg

Gabriel Egolf wrote:

Hello all.

I'm in the last stages of development on a rather large

project, and for


some time now have been plagued by a rather annoying problem.  I'm not
sure even how the problem began, but I'll try to give as much
information as possible and hopefully one of you has run across it in
the past.  Generally, the problem manifests itself as a blank page
containing nothing but the XML PI (<?xml version="1.0"
encoding="utf-8"?>).  Occasionally, I'll get the contents of 2

unrelated


pages together.  Unfortunately, this problem seems to be a completely
random occurence, and usually a server restart will solve it

temporarily.


Here's my software environment:
JDK 1.4.1_02
Jetty 4.2.9
Cocoon 2.0.4

I've supplied an error trace from my error.log at the end of this
message.  If you've seen this before, please let me know how

you fixed it.


Thanks.

Gabriel Egolf


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



Reply via email to