EAServer can load and execute a Java class file as a component. The class can be a standalone class or part of a JavaBeans component that does not display any graphics or text, that is, a nonvisual JavaBeans component.
The definition of a Java component specifies the interfaces that the component implements as well as its other properties.
All component interfaces for EAServer components are defined in CORBA IDL modules that are stored in the EAServer IDL repository. Chapter 3, “Using CORBA IDL,” in the EAServer CORBA Components Guide describes how to define IDL interfaces.
Java component developers typically use one of the following to define the interface or interfaces that their component implements:
Use existing interfaces from the EAServer IDL repository In some cases, client and server component developers may have agreed upon one or more interfaces that a component must implement. In this case, it is up to the component developer to implement any specified interfaces. EAServer stores HTML documentation for all interfaces in the IDL repository in the html/ir subdirectory of the EAServer installation.
Define one or more new IDL interfaces If you are defining the interface yourself, you can use a text editor to create a new interface for the component. See Chapter 3, “Using CORBA IDL,” in the EAServer CORBA Components Guide.