Application client functions

Application client functions

Use this table to detemine which application client best suits your needs:

Available functions ActiveX client Applet client J2EE client Pluggable client Thin client

Provides all the benefits of a J2EE platform Yes No Yes No No

Portable across all J2EE platforms No No Yes No No

Provides the necessary run time to support communication between client and server Yes Yes Yes Yes Yes

Allows the use of nicknames in the deployment descriptors Yes No Yes No No

Supports use of the RMI-IIOP protocol Yes Yes Yes Yes Yes

Browser based application Yes* Yes No No No

Enables development of client applications that can access enterprise bean references and CORBA object references Yes Yes Yes Yes Yes

Enables the initialization of the client application runtime environment Yes No Yes No No

Supports security authentication to enterprise beans Yes Limited Yes Yes Yes

Supports security authentication to local resources Yes No Yes No No

Requires distribution of application to client machines Yes* No Yes Yes Yes

Enables access to enterprise beans and other Java classes through Visual Basic, VBScript, and Active Server Pages (ASP) code Yes No No No No

Provides a lightweight client suitable for download Yes* Yes No Yes Yes

Enables access to Java Naming and Directory Interface (JNDI) for enterprise bean resolution No Yes Yes Yes Yes

Runs on client machines that use the Sun Java Runtime Environment No No No Yes No

Supports CORBA services (using CORBA services can render the application client code Nonportable) No No Yes No No

*The ActiveX client is suitable for download, because ASP and VB classes can be run inside of a an HTML page, just like an applet. It is both suitable for download and does not require distribution to client machines. However, stand-alone VB programs are not suitable for download.

Available functions	ActiveX client	Applet client	J2EE client	Pluggable client	Thin client
Provides all the benefits of a J2EE platform	Yes	No	Yes	No	No
Portable across all J2EE platforms	No	No	Yes	No	No
Provides the necessary run time to support communication between client and server	Yes	Yes	Yes	Yes	Yes
Allows the use of nicknames in the deployment descriptors	Yes	No	Yes	No	No
Supports use of the RMI-IIOP protocol	Yes	Yes	Yes	Yes	Yes
Browser based application	Yes*	Yes	No	No	No
Enables development of client applications that can access enterprise bean references and CORBA object references	Yes	Yes	Yes	Yes	Yes
Enables the initialization of the client application runtime environment	Yes	No	Yes	No	No
Supports security authentication to enterprise beans	Yes	Limited	Yes	Yes	Yes
Supports security authentication to local resources	Yes	No	Yes	No	No
Requires distribution of application to client machines	Yes*	No	Yes	Yes	Yes
Enables access to enterprise beans and other Java classes through Visual Basic, VBScript, and Active Server Pages (ASP) code	Yes	No	No	No	No
Provides a lightweight client suitable for download	Yes*	Yes	No	Yes	Yes
Enables access to Java Naming and Directory Interface (JNDI) for enterprise bean resolution	No	Yes	Yes	Yes	Yes
Runs on client machines that use the Sun Java Runtime Environment	No	No	No	Yes	No
Supports CORBA services (using CORBA services can render the application client code Nonportable)	No	No	Yes	No	No