Re: Java and V6R1 Odd Problem?

James Perkins skrev:

Thorbjørn,
That would make sense. I have my own class that's like the PropDump, but it
also dumps some runtime information too. I got some odd results with that
too. While it worked both ways, when the processors available prints, it
prints 4 without the -D parameter and 2 with the parameter.

So I would assume the overrides force the classic JVM?

An instructional video wouldn't hurt. I'm always willing to learn/understand
something better.

James R. Perkins

I would have a very close look in the infocenter regarding the new behaviour of the Java system. It is probably very well documented, if you happen to know beforehand what you are looking for.

I'm looking around for a good screencast capture program, Jing does not allow postprocessing sigh, so no video today. I have destilled the approach I use in our swiss army knife jar in these two snippets, where Main will be the class set as entry point in the executable jar.

Hopefully it is useful.

====
package com.runjva.demo;

import java.util.Iterator;
import java.util.Map;
import java.util.TreeMap;


public class PropDump {
/**
* @param args
*/
public static void main(String[] args) {
Map map = new TreeMap(System.getProperties());
for (Iterator iterator = map.entrySet().iterator(); iterator.hasNext();) {
Map.Entry type = (Map.Entry) iterator.next();
System.out.println(type.getKey() + " = " + type.getValue()); }
}
}
=====

package com.runjva.demo;


public class Main {

/**
* @param args
*/
public static void main(String[] args) {
String command = args[0];
String[] argsOnly = new String[args.length - 1];
for (int i = 0; i < argsOnly.length; i++) {
argsOnly[i] = args[i + 1];
}

if (command.equals("PropDump")) {
PropDump.main(argsOnly);
} else {
System.out.println("unsupported command: " + command);
}
}

}