Hi I have been doubtful on which mailing list to use for this post. I've choosen Turbine-user, hope I've choosen well... I'have recently installed Jetspeed-1.4b1 (based on Turbine-2.2b2) on JBoss-3.0.4-Tomcat-4.0.6. I've not tested everything yet, hopefully I'll do it a.s.a.p. The first thing I've noticed is the logging being diverted from the JBoss standard location to the Jetspeed /WEB-INF/log/jetspeed.log. Somebody else before me has noticed this. In an archived email of Jetspeed-user mailing list, from Werner Ramaekers on 29-Nov-2002, I read: " Jetspeed is running fine if you have set it up like described there. All the Jetspeed logging goes to Jetspeed/WEB-INF/log/jetspeed.log so it is normal if you don't see any logging in the jboss console log. " I haven't found any more replies about that, but I question that Jetspeed's (Turbine's) logging behaviour in JBoss infrastructure is not 100% acceptable. I can see that this behaviour comes from Turbine-2.2.x, which reconfigures the Log4j RootLogger with the settings of tr.props, regardless somebody else has already configured it for some other purposes (JBoss in this case...). This means that the last Turbine-based web-app deployed in JBoss will gather all JBoss system's an deployed web-app's log messages within its logging device (file). Moreover the JBoss standard behaviour to log message on the console is suddenly turned off without it being explicitly set by the user. I would rather accept either the web-app storing its logging on a separate file from JBoss with its own settings, or, at least, on the JBoss logging file (being the web-app a component of the overall system).
Just my opinion, and a question: is there a trick to log Turbine-based web-app (Jetspeed in this case) on its own log file? T.I.A. Alberto Trentadue Software engineer [EMAIL PROTECTED]
