Is contextInitialized() blocked from setting System properties?

Question

A certain 3rd party app we're using within a web app requires a specific System
property be set. Since it's a local path, we'd like to shy away from hardcoding
a -D into the startup script, and instead do it via a ServletContextListener and
set the property within contextInitialized(). In WL7.0sp2, it seems to hit the
line in our listener where it tries to set a System property, and nothing happens.
It doesn't seem to throw an exception, write anything to the console, nothing.
Is there a security setting that blocks contextInitialized() methods from setting
System properties? Is it a WL thing, or maybe a servlet spec thing? It works
if we use a dummy servlet set to pre-load, where we set the System property in
the servlet's init() method, but that's a little tackier than doing it in one
single context init listener.

Answer 1

Turns out the context-param that I was trying to use as the value of the System
property was null. When it sets a non-null value, it works. But apparently when
the value of the System property is null, you get the weird behaviour described
below: it's as if the tread just stops. I tried setting a breakpoint and stepping
through, but it immediately went into weblogic security and threading classes
and never returned. So now I'll have a new question about when context-params
load during deployment, but I'll post that separately.
"Mark Griffith" <[email protected]> wrote:
I don't know of any restriction. Your saying it never sets it? The
app
deploys but it is not there in the system properites?
Have you tried setting a break point and stepping?
Very strange.
mbg
"dave thompson" <[email protected]> wrote in message
news:3ecac0f8$[email protected]..
A certain 3rd party app we're using within a web app requires a specificSystem
property be set. Since it's a local path, we'd like to shy away fromhardcoding
a -D into the startup script, and instead do it via aServletContextListener and
set the property within contextInitialized(). In WL7.0sp2, it seemsto
hit the
line in our listener where it tries to set a System property, and nothinghappens.
It doesn't seem to throw an exception, write anything to the console,nothing.
Is there a security setting that blocks contextInitialized() methodsfrom
setting
System properties? Is it a WL thing, or maybe a servlet spec thing?It
works
if we use a dummy servlet set to pre-load, where we set the Systemproperty in
the servlet's init() method, but that's a little tackier than doingit in
one
single context init listener.