Brian Leonard wrote: > Uh, thanks. The problem was that catalina, running as root, could > write to any log file all day long. IWS, running as 'nobody', didn't > have write perms to the directory I had pointed it at back when I > started writing the app. The loggers eat exceptions and dump errors > to stdout and sterr, which go nowhere particularly obvious with iws. > So, these two patches. It seems to me that throwing an informative > exception up to the app is kinder than what it does now. I think that those patches are reasonable - would anyone be horrified if an exception actually came out of init()? I do think I would keep the System.out. and System.err messages for now in the event that people's try/catch blocks around init() aren't good. I am going to try to configure things so this happens under tomcat, and see what it looks like. I don't think that there would be any problems adding this to 1.1, as we are simply letting the exception propogate out. The public o.a.v.r.Runtime and o.a.v.a.Velocity APIs don't change... Any contrary opinions welcome. geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ "still climbing up to the shoulders..."
