cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Purvis <>
Subject CNFException(s) not logged anywhere and causing confusion for all users
Date Fri, 06 Jun 2003 06:21:54 GMT
morning all, 

- linux Redhat 8.0 (kernel 2.4.19)
- SUN jdk1.4.2 (and even back to 1.4.0)
- cocoon 2.1m2 (and even back to early 2.1 CVS snapshots)

i have found that when cocoon is missing classes (and all other things
being setup correctly) it doesn't generate any logged exception that i
can find. The result is a very puzzling situation. I post because ive
found many people with the same situation (many relating to the
xalan.jar and $TOMCAT_HOME/lib/endorsed fiasco, but this is just a
common example of the problem). Ive turned all the logging levels down
to DEBUG with no visible evidence of the fact that my app was missing
classes. Ive even checked the tomcat log files and found nothing.
Nothing output to stdout either. 

Ive run into this in 2 similiar situations both leading me to believe
its a situation where classes are missing from the classpath. 

1 - the classic xalanXXX.jar problem with the older libraries pointing
to non-existent classes. In this case i get nothing but blank screens
when trying to request uri(s) that are perfectly sound. 

2 - when certain custom actions were missing SUPPORTING class files. 

by dropping the correct classes in /WEB-INF/classes or jars in
/WEB-INF/lib the problem is solved and all the uris load properly. These
missing classes seem to disable any map:match in the sitemap regardless
of whether the match is affected by the missing classes. I dont even get
ANY output from the requested uris. (i.e. not even empty <html></html>
tags from a match terminated with an HTMLSerializer.)

so the question then concerns whether this is a bug or not ? I know i
have wasted more time than i would have liked coming to this
realization. Ive also seen MANY people with similar problems that have
resulted in no exceptions in the logs and no output on requests. 

at the very least shouldnt this be documented somewhere so its a bit
less confusing. 

have i missed something ?


View raw message