Another solution could be a simple shutdown with the valid error message. Sometimes the error message is better than hidden behaviour. So the alternative is to check all properties VM needs before running real startup and fail if some of the properties are not found.
On 10/10/06, Evgueni Brevnov <[EMAIL PROTECTED]> wrote:
Hi All, Currently DRLVM starts with help of the launcher. The launcher does a lot of stuff required to create VM instatnce. As a part of its job it sets up java.class.path property. And this is good. What is not good that DRLVM crashes (actually throws NullPointerException in initalization stage) if java.class.path is not set. I believe it makes sense to point java.class.path to current directory inside VM if launcher doesn't set it. What do u think? Thanks Evgueni --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mikhail Fursov
