Michael,
On Wed, Apr 30, 2008 at 5:34 AM, Michael Roberts <
mroberts@...> wrote:
> The problem occurs because the Orbeon webapp sets a system property named
> "log4j.configuration" in the org.orbeon.oxf.util.LoggerFactory. Because
> this value is deliberately set to a bogus value, any webapps in the same JVM
> (same tomcat in this case) that start after Orbeon, will fail using the
> regular configuration discovery mechanisms of Log4j.
>
> I am not sure if the conditions for this design decision are still present.
> They might be. My opinion is that any webapp that sets a system property
> better have an extremely good reason for doing so, given that system
> properties are shared across the entire JVM, not just webapp.
Indeed, I agree that setting a system property can be considered to be
reasonably evil and I am not sure we still have a good reason do that.
Have you tried removing that call to System.setProperty(
"log4j.configuration", "-there-aint-no-such-file-" )? If you have, can
you confirm that everything is working fine without it?
Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog:
http://www.orbeon.com/blog/Personal Blog:
http://avernet.blogspot.com/Twitter -
http://twitter.com/avernet--
You receive this message as a subscriber of the
ops-users@... mailing list.
To unsubscribe: mailto:
ops-users-unsubscribe@...
For general help: mailto:
sympa@...?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws
