03 Troubleshooting
Designer
Embedded Java Applet issues
- There is a 32K limit for an Applet Shared resource in Domino Designer. There is a list of the files that is part of the resource in a field and this field must be less than 32K bytes. The workaround for the size limitation here is to split these files into separate resources.
- There is a 64K size limit for Imported Java Applet Files. The combined amount of data stored with the applet (which includes the signature information, the applet parameter information, and list of all of the files associated with the applet) is limited to 64K bytes.
- Canceling the paste of a parameter value may not revert it to its original value. When you have more than one applet parameter, pressing "x" to cancel the paste operation of a subsequent value replaces the value with that of the first parameter.
- Loading and reloading large Java applets leads to "out of memory" conditions. A workaround is to use JavaUserClasses in NOTES.INI to load all or most of the classes. This ensures the classes are loaded only once, so there is no significant heap size expansion for every applet instance that is loaded. There may be replication problems with this workaround because it relies on classes loaded from the file system, which is outside of Designer's control.