You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Evgueni Brevnov (JIRA)" <ji...@apache.org> on 2006/10/11 09:16:19 UTC
[jira] Created: (HARMONY-1818) [drlvm] VM throws
NullPointerException in case java.class.path is not set
[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 <ol...@googlemail.com> to harmony-dev
I have just tried launching the RI with a simple launcher (very basic -
CreateJavaVM(),
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) {
System.getProperties().list(System.out);
}
}
The java.class.path value is printed as:
java.class.path=
So it appears that java.class.path property is left empty by default.
However,
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
current
directory. So although the java.class.path is set to an empty string,
internally
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.
Regards,
Oliver
--
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
[jira] Updated: (HARMONY-1818) [drlvm] VM throws
NullPointerException in case java.class.path is not set
Posted by "Geir Magnusson Jr (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-1818?page=all ]
Geir Magnusson Jr updated HARMONY-1818:
---------------------------------------
Component/s: DRLVM
> [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
> Components: DRLVM
> Environment: All
> Reporter: Evgueni Brevnov
> Attachments: simpleLaunch.c, SysInfo.java
>
>
> 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 <ol...@googlemail.com> to harmony-dev
> I have just tried launching the RI with a simple launcher (very basic -
> CreateJavaVM(),
> 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) {
> System.getProperties().list(System.out);
> }
> }
> The java.class.path value is printed as:
> java.class.path=
> So it appears that java.class.path property is left empty by default.
> However,
> 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
> current
> directory. So although the java.class.path is set to an empty string,
> internally
> 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.
> Regards,
> Oliver
--
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
[jira] Closed: (HARMONY-1818) [drlvm] VM throws
NullPointerException in case java.class.path is not set
Posted by "Geir Magnusson Jr (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-1818?page=all ]
Geir Magnusson Jr closed HARMONY-1818.
--------------------------------------
> [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
> Components: DRLVM
> Environment: All
> Reporter: Evgueni Brevnov
> Assigned To: Geir Magnusson Jr
> Attachments: simpleLaunch.c, SysInfo.java
>
>
> 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 <ol...@googlemail.com> to harmony-dev
> I have just tried launching the RI with a simple launcher (very basic -
> CreateJavaVM(),
> 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) {
> System.getProperties().list(System.out);
> }
> }
> The java.class.path value is printed as:
> java.class.path=
> So it appears that java.class.path property is left empty by default.
> However,
> 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
> current
> directory. So although the java.class.path is set to an empty string,
> internally
> 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.
> Regards,
> Oliver
--
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
[jira] Updated: (HARMONY-1818) [drlvm] VM throws
NullPointerException in case java.class.path is not set
Posted by "Oliver Deakin (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-1818?page=all ]
Oliver Deakin updated HARMONY-1818:
-----------------------------------
Attachment: SysInfo.java
simpleLaunch.c
I am attaching the basic java launcher and the java class described in my post to the -dev list quoted above.
> [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
> Attachments: simpleLaunch.c, SysInfo.java
>
>
> 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 <ol...@googlemail.com> to harmony-dev
> I have just tried launching the RI with a simple launcher (very basic -
> CreateJavaVM(),
> 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) {
> System.getProperties().list(System.out);
> }
> }
> The java.class.path value is printed as:
> java.class.path=
> So it appears that java.class.path property is left empty by default.
> However,
> 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
> current
> directory. So although the java.class.path is set to an empty string,
> internally
> 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.
> Regards,
> Oliver
--
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
[jira] Resolved: (HARMONY-1818) [drlvm] VM throws
NullPointerException in case java.class.path is not set
Posted by "Geir Magnusson Jr (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-1818?page=all ]
Geir Magnusson Jr resolved HARMONY-1818.
----------------------------------------
Resolution: Fixed
r474197
Ubuntu 6 - smoke, c-unit, ~kernel
> [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
> Components: DRLVM
> Environment: All
> Reporter: Evgueni Brevnov
> Assigned To: Geir Magnusson Jr
> Attachments: simpleLaunch.c, SysInfo.java
>
>
> 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 <ol...@googlemail.com> to harmony-dev
> I have just tried launching the RI with a simple launcher (very basic -
> CreateJavaVM(),
> 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) {
> System.getProperties().list(System.out);
> }
> }
> The java.class.path value is printed as:
> java.class.path=
> So it appears that java.class.path property is left empty by default.
> However,
> 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
> current
> directory. So although the java.class.path is set to an empty string,
> internally
> 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.
> Regards,
> Oliver
--
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
[jira] Assigned: (HARMONY-1818) [drlvm] VM throws
NullPointerException in case java.class.path is not set
Posted by "Geir Magnusson Jr (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-1818?page=all ]
Geir Magnusson Jr reassigned HARMONY-1818:
------------------------------------------
Assignee: Geir Magnusson Jr
> [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
> Components: DRLVM
> Environment: All
> Reporter: Evgueni Brevnov
> Assigned To: Geir Magnusson Jr
> Attachments: simpleLaunch.c, SysInfo.java
>
>
> 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 <ol...@googlemail.com> to harmony-dev
> I have just tried launching the RI with a simple launcher (very basic -
> CreateJavaVM(),
> 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) {
> System.getProperties().list(System.out);
> }
> }
> The java.class.path value is printed as:
> java.class.path=
> So it appears that java.class.path property is left empty by default.
> However,
> 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
> current
> directory. So although the java.class.path is set to an empty string,
> internally
> 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.
> Regards,
> Oliver
--
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