Would it be a compatible change to introduce a new interface, which Applet implements (for discussion purposes, let's call it IApplet), and change the signature of AppletInitializer to take IApplet instead of Applet?
--Rich Unger 01:57, 16 June 2009 (CEST)
Hello Rich, thanks for your note. To make things better, the IApplet would have to be defined in java.beans module. Moreover it would not be compatible to change the method signature in AppletInitializer, there would have to be new AppletInitializer2 that would take IApplet. This could work, but I am horrified: I've just found out that there is a static method in Beans class that takes AppletInitializer as an argument. That is unexpected complication.
Follow
Would it be a compatible change to introduce a new interface, which Applet implements (for discussion purposes, let's call it IApplet), and change the signature of AppletInitializer to take IApplet instead of Applet?
--Rich Unger 01:57, 16 June 2009 (CEST)
Hello Rich, thanks for your note. To make things better, the IApplet would have to be defined in java.beans module. Moreover it would not be compatible to change the method signature in AppletInitializer, there would have to be new AppletInitializer2 that would take IApplet. This could work, but I am horrified: I've just found out that there is a static method in Beans class that takes AppletInitializer as an argument. That is unexpected complication.
--JaroslavTulach 14:22, 16 June 2009 (UTC)