Use the following guidelines when you consider whether to deploy your custom Java™ Step or Launch Processor as an application or an applet:
Feature | Deployed as application | Deployed as applet |
---|---|---|
Step Processor opening | The Step Processor must implement an applet class in order to open the step assignment from an email notification message. | A Java Step Processor
can be opened from an email notification message. A Launch Processor cannot be opened from an email notification message. There is no need to implement an applet class if you are deploying the Launch Processor as an application. |
User Inbox display refreshing when you complete or close a step | The User Inbox automatically refreshes its display. This refresh occurs when the application notifies the User Inbox of the step completion or closure event. | The user must manually refresh the User Inbox to refresh its display. |
Session sharing | An application enables a session to be shared: the user is not required to log in again. Your application class must implement the IVWLaunchableApp interface, either directly or by extending the VWBaseLaunchableApplication class (as in the Java Step and Launch Processor samples). | |
Modal popup windows | Popup dialogs must be modal. Modal dialogs prevent users from doing something else outside the dialog box while the dialog entry is unresolved. | An applet does not provide dialog modality. |
Java plugin usage | The application can use the same instance of the Java plugin. |
The applet must create a new instance of the Java plugin, which slows performance. |