Tell me something about Local Interfaces.
EJB was originally designed around remote invocation using the Java Remote Method Invocation (RMI) mechanism, and later extended to support to standard CORBA transport... Read more »
EJB was originally designed around remote invocation using the Java Remote Method Invocation (RMI) mechanism, and later extended to support to standard CORBA transport... Read more »
The J2EE Connector API is used by J2EE tools vendors and system integrators to create resource adapters that support access to enterprise information systems that... Read more »
JAXP stands for Java API for XML. XML is a language for representing and describing text-based data which can be read and handled by any program or tool that uses... Read more »
JTA is the abbreviation for the Java Transaction API. JTS is the abbreviation for the Jave Transaction Service. JTA provides a standard interface and allows you... Read more »
An EAR file is a standard JAR file with an .ear extension, named from Enterprise ARchive file. A J2EE application with all of its modules is delivered in EAR file. Read more »
Following are the types of J2EE clients: Applets Application clients Java Web Start-enabled rich clients, powered by Java Web Start technology. Wireless clients,... Read more »
A thin client is a lightweight interface to the application that does not have such operations like query databases, execute complex business rules, or connect to... Read more »
J2EE components are packaged separately and bundled into a J2EE application for deployment. Each component, its related files such as GIF and HTML files or server-side... Read more »
It manages the execution of Applets and contains Web Browser and java Plugging running simultaneously on Client. Read more »
It manages the execution of enterprise beans for J2EE applications. Enterprise beans and their container run on the J2EE server. Read more »
No. Static HTML pages and applets are bundled with web components during application assembly, but are not considered web components by the J2EE specification. Even... Read more »
No. JavaBeans components are not considered J2EE components by the J2EE specification. They are written to manage the data flow between an application client or... Read more »
No, It depends on type of application that client wants. A J2EE application can be web-based or non-web-based. if an application client executes on the client machine,... Read more »
Enterprise JavaBeans components contains Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or... Read more »
In 3-tier architecture, an application is broken up into 3 separate logical layers, each with a well-defined set of interfaces. The presentation layer typically... Read more »