harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgueni Brevnov (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-1818) [drlvm] VM throws NullPointerException in case java.class.path is not set
Date Wed, 11 Oct 2006 07:16:19 GMT
[drlvm] VM throws NullPointerException in case java.class.path is not set 

                 Key: HARMONY-1818
                 URL: http://issues.apache.org/jira/browse/HARMONY-1818
             Project: Harmony
          Issue Type: Improvement
         Environment: All
            Reporter: Evgueni Brevnov

Evgueni Brevnov  to harmony-dev 

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.

 Oliver Deakin  <oliver.deakin@googlemail.com> to harmony-dev 

I have just tried launching the RI with a simple launcher (very basic -
finds and launches a class, then calls DestroyJavaVM()). The launcher
does not
set java.class.path, and executes the main method of the following class:

  public class SysInfo {
      public static void main(String[] args) {

The java.class.path value is printed as:


So it appears that java.class.path property is left empty by default.
to have found the SysInfo class, the RI must have searched in the current
directory. I can also instantiate other classes that are located in the
directory. So although the java.class.path is set to an empty string,
there is a default inclusion of the current directory.

IMHO we follow the RI behaviour here, and have an implicit inclusion of
the current directory unless the classpath is explicitly set.


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message