Problems with Oracle Forms 6 Recording Using Additional Java Beans

Implementing Java Beans can extend Oracle Forms applications with new GUI-Elements or Client-Side functionality. Those Java extensions will be downloaded by the client applet at startup.

When recording Oracle Forms 6, Silk Performer's Recorder will hook the main Java Archive containing the applet classes. The Java extensions either derive from classes or implement an interface that is contained within this archive. The Java Runtime, depending on some configuration settings, will verify class signatures when loading those Java Beans. As the main archive has been modified, those verifications will fail and the applet will no longer start.

To disable this verification process it is necessary to define an additional Java runtime parameter in the JInitiator Runtime Parameter settings. Define the parameter -noverify in your JInitiator settings.