Java/M Technical Ingredients

This page describes some of the Java classes used to support user sign-on and form displays.  It is to give more detail on how I setup some objects and *NOT* meant to be a tutorial.

Warning: Only view this material if you are a Java programmer...

These are the main objects for using Java and M (client side):

1) object uses the Session object to begin a user session.  Sign-on basically initiates the session and closes the Java application when a session ends.  This is the source code for the Sign-on screen used in the demo.  It can be used as an application or applet and it also demonstrates how the Session can be used to begin a session.

2) object displays the sign-on screen, triggers session events, and communicates to the ORB server to validate codes.  It sets up the "user" environment very similar to the kernel sign-on process with VISTA.

3) object provides tools necessary to display application forms in a consistent manner.  This is analogous to the menu management part of VISTA.

4) object is an application form designed by the application programmer.  It must support specific functions to displayed on the workbench.  When an item is displayed on the workbench, it is functions are "merged" with the workbench to provide a consistent user-interface.

5) object is the Play form used in our demo section.  It demonstrates an application form interacting with the Kernel Workbench.  It also demonstrates the ability to display the form when the "Show Form 2" menu item is selected.

These are the main objects (IDLs) for using Java and M (server side):

1) Logon.idl represents the logon of the user to the VISTA system.

2) LogonManager.idl handles requests for logon and logouts to the server.

3) ServerToolKit.idl provides functions from the client to the server that may or may not be associated to a user logon.

4) User.idl represents the user that is logged onto.

[Home Page] [VISTA Demonstration] [Java Links]
[Technical Diagrams] [Technical Ingredients]