On Jul 22, 2009, at 12:23 PM, David Jencks wrote:
There are two possibilities I can think of right now:
1. Something is calling Environment.setApplicationProperties(null)
which produces a NullPointerException before the System.out can tell
you about it. This seems unlikely but is easy to check with another
System.out. I guess there might be a clearApplicationProperties()
method also...
2. you have 2 classloaders loading the Environment class. I don't
really see how this would be happening either but again is pretty
easy to check.
That was the only "idea" that I had...
You should be able to reproduce this under the Eclipse Debugger.
Launch the server process remotely (i.e. 'bin/geronimo.sh jpda run'),
attach the Eclipse process to this server process (e.g. localhost port
8000), set breakpoint(s), and run a deploy.
--kevan
