You could always check the cvs/svn history and see who added
that code and ask them why they added it. :-)
Bobby Bissett wrote on 05/06/2010 10:05 AM:
> On May 5, 2010, at 7:54 PM, Bill Shannon wrote:
>> Why don't you just ignore the exception from System.getenv?
>> We're not expecting these environment variables to be set in
>> the normal case, are we?
>
> I can't answer those questions any better than you, :)
>
>> It looks like the code just tries
>> to find it as a System property, and if that fails tried to
>> find it as an environment variable as some sort of fallback.
>
> Really, I was just getting confirmation that anyone cared before looking
> at it further. If it's the case that the property really isn't needed,
> then ignoring the exception is fine. Not making the call in the first
> place would be better, but maybe there's a use case for it. Not my place
> to say, but I'll give it a shot and see where we get.
>
> FWIW, this isn't an issue with the server.policy file as far as I can
> tell. I think this code is operating before the policy system has been
> started.
>
> Cheers,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>