design. develop. deploy.
According to our documentation (sdkj_userguide_eRxxx.pdf, around page 16), a J522 error is an extended feature startup failed problem. In this case, most of the time, a problem is in the life cycle method initXlet(). Some things to keep in mind are the execution time of the life cycle methods. If the application takes longer than specified by the specification to execute errors like J522 may occur.
Seems like the UI is busy and the application will have to retry to make the switch.
I'm able to replicate in my lab with a quick switch to button and at times it may take up too 5 tries. Can you create the workaround to attempt a retry until successful or until a timeout occurs.
See code snippet below:
The J301 Errors typically occur as part of the installation process.
In sdkj_userguide_exxx.pdf error cause is defined as installation destination invalid and other errors.
The most common causes are:
1. The application was not signed properly.
2. There was a mismatch of the product id between the dalp file and the signature.
What we provide is actually a subset of the JCE. It isn't a fully functional, compliant JCE. So, the default encryption algorithm is the only one which is available on the MFP. On older MFPs RSA is the default encryption algorithm.
SDK/J versions 5.x, 6.x, 7.x, 10.x, 11.x and 12.x supports AES128 for SSL communication from within your SDK/J Servlet application. 11A and later models support SHA-256 and SHA-512 through a device certificate. These certificates are generated in Web Image monitor and/or are uploaded.
HVGA is the default panel size. Documentation on this topic is found on sdkj_xlet_develop_panel_eR112.pdf (page 12). This document section describes the default behavior regarding display panel and DALP file correlation. The document notes the following:
Issue:
The FileAllocator xlet attached to this incident fills up the hard drive with temporary files so you can test your application in an environment where there is not enough disk space remaining for an operation.
The zip file's folder structure should be flat In with all files at top of tree. In other words, there should not be a folder structure inside the zip file. The correct folder structure for the application install zip file uses the following format:
app.zip
./app.dalp
./app.jar
./opt1.jar