I updated my JDK to 1.3.1_07 and ran across a strange bug with -classic. JBoss won't
even startup when -classic is enabled because the File.getCanonicalPath method is
returning the wrong value:
---------- BEGIN SOURCE ----------
import java.io.File;
class tstPath2
{
public static void main(String[] args) throws Exception
{
String path =
tstPath2.class.getProtectionDomain().getCodeSource().getLocation().getFile();
System.out.println("tstPath2.class path: "+path);
File dir = new File(path).getParentFile().getParentFile();
String cdir = dir.getCanonicalPath();
System.out.println("../../CanonicalPath: "+cdir);
}
}
---------- END SOURCE ----------
Run without -classic:
Tests 593>java tstPath2
tstPath2.class path: /C:/usr/local/Java/Tests/
../../CanonicalPath: C:\usr\local
Run with -classic:
Tests 594>java -classic tstPath2
tstPath2.class path: /C:/usr/local/Java/Tests/
../../CanonicalPath: C:\usr\local\Java\Tests
Fortunately the debubugging does not seem to be as slow as it used to be without
-classic
with JDK1.3.1_07 so removing the -classic arg from the JPDA settings allows you to
debug.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
