Bad news, Tao Group isn't PBP-1.0 complaint.
Their java.awt.Window has a constructor, PBP-1.0 says it has no constructor.
I worked around this by crafting a java.awt.Window to compile against that has the Tao Group constructor so I could invoke it.
But when run I get:
Code:
[Loaded java/awt/Dialog/class]
[Loaded java/awt/Insets/class]
[Loaded java/lang/UnsupportedOperationException/class]
[Loaded java/lang/reflect/InvocationTargetException/class]
app/stdio/jcode: (*env)->CallStaticVoidMethod returned an exception
java.lang.UnsupportedOperationException
java.awt.GraphicsDevice.claimWindow(Ljava/awt/Window;)V
java.awt.Window.<init>(Ljava/awt/GraphicsConfiguration;Ljava/awt/Window;)V
java.awt.Dialog.<init>(Ljava/awt/Frame;Ljava/lang/String;Z)V
java.awt.Dialog.<init>(Ljava/awt/Frame;Ljava/lang/String;)V
test3.<init>()V
test3.main([Ljava/lang/String;)V
I tried having Dialog extend Frame instead of Window and got the same issue.
According to PBP-1.0 we are restricted to a single Frame per application, but there is no restriction on the number of Windows. Therefore Tao Group's JVM is not fully PBP-1.0 compliant.
And because it isn't: no Dialogs.
P.S. No, the javac compiler won't let me wrap the super(...) in a try/catch block.