----- Original Message -----
From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
To: "Apache Cocoon" <[EMAIL PROTECTED]>
Sent: Wednesday, December 05, 2001 4:09 PM
Subject: Bug reports


> I'm finally getting my hand dirty again with the CVS HEAD.
>
> A few things that bug me:
>
> 1) java.sql.SQLException: File input/output error: C:\Program
> Files\Apache Tomcat 4.0\webapps\cocoon\WEB-INF\db\cocoondb.backup
> at org.hsqldb.Trace.getError(Trace.java:180)
> at org.hsqldb.Trace.getError(Trace.java:144)
> at org.hsqldb.Trace.error(Trace.java:205)
> at org.hsqldb.Log.restoreBackup(Log.java:731)
> at org.hsqldb.Log.open(Log.java:212)
> at org.hsqldb.Database.<init>(Database.java:96)
> at org.hsqldb.Server.run(Server.java:137)
> at org.hsqldb.Server.main(Server.java:78)
> at
> org.apache.cocoon.components.hsqldb.ServerImpl.run(ServerImpl.java:101)
> at java.lang.Thread.run(Thread.java:484)
>
> I've never been able to make the db work. Have you ever experienced
> this?

Yes, since it became an Avalon component.
Have tried everyting i can think of, including removing the driver loading
from
xconf before building the webapp. No results though. Since we´ve prosponed
our release of our c2 based, I haven´´t really put that much of an effort
into it, but
if there is a simple answer, I´d like to hear it ;-)

<snip>

> 9) I get a bunch of NPE out of a missing SAXConnector even if I didn't
> enable no logging or profiling. BTW, we shouldn't get NPE out of
> component managers since throwing/catching exception is an expensive
> operation for the JVM.

According to a friend of mine, doing extensive performance tests on java
patterns,
trapping a nullpointer with try/catch rather than with an if-statement is
VERY bad.
His number on this was 700 times slower with try/catch


Regards,

Per-Olof


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

Reply via email to