Explore topic-wise InterviewSolutions in Current Affairs.

1.The local CLIENT view specification is only available in EJB 2.0. UNLIKE the remote client view, the local client view of a bean is location dependent.
2.Local client view access to an ENTERPRISE bean requires both the local client and the enterprise bean that provides the local client view to be in the same JVM.
3.The local client view therefore does not provide the location TRANSPARENCY provided by the remote client view. Local interfaces and local home interfaces provide support for lightweight access from enterprise bean that are local clients.
4.Session and entity beans can be tightly couple with their clients, allowing access without the overhead typically associated with remote method calls.

1.The local client view specification is only available in EJB 2.0. Unlike the remote client view, the local client view of a bean is location dependent.
2.Local client view access to an enterprise bean requires both the local client and the enterprise bean that provides the local client view to be in the same JVM.
3.The local client view therefore does not provide the location transparency provided by the remote client view. Local interfaces and local home interfaces provide support for lightweight access from enterprise bean that are local clients.
4.Session and entity beans can be tightly couple with their clients, allowing access without the overhead typically associated with remote method calls.

1.The REMOTE client view specification is only AVAILABLE in EJB 2.0.
2. The remote client view of an enterprise bean is location independent.
3.A client running in the same JVM as a bean instance uses the same API to access the bean as a client running in a DIFFERENT JVM on the same or different machine.
Remote interface: The remote interface specifies the remote business methods that a client can call on an enterprise bean.
Remote home interface: The remote home interface specifies the methods used by remote clients for locating, CREATING, and removing instances of enterprise bean classes.

1.The remote client view specification is only available in EJB 2.0.
2. The remote client view of an enterprise bean is location independent.
3.A client running in the same JVM as a bean instance uses the same API to access the bean as a client running in a different JVM on the same or different machine.
Remote interface: The remote interface specifies the remote business methods that a client can call on an enterprise bean.
Remote home interface: The remote home interface specifies the methods used by remote clients for locating, creating, and removing instances of enterprise bean classes.

An EJB CLIENT JAR file is an optional JAR file that can contain all the CLASS files that a client program needs to USE the client VIEW of the ENTERPRISE beans that are contained in the EJB JAR file. If you decide not to create a client JAR file for an EJB module, all of the client interface classes will be in the EJB JAR file.

An EJB client JAR file is an optional JAR file that can contain all the class files that a client program needs to use the client view of the enterprise beans that are contained in the EJB JAR file. If you decide not to create a client JAR file for an EJB module, all of the client interface classes will be in the EJB JAR file.

CONTAINER SERVICES are totally DEPENDS upon the “vendor implementation”. But more or less most of the vendors suppots the basic services LIKE,
LifeCycle Management - It is Automatic.
Session Management - it is used by Developer CODED callback methods…
Transaction Management - it is used by configuring deployment descriptor (DD) .
Security management - it is used by configuring deployment descriptor (DD) .
The other services, if any will be in advanced versions, and depends on Vendor specific.

Container services are totally depends upon the “vendor implementation”. But more or less most of the vendors suppots the basic services like,
LifeCycle Management - It is Automatic.
Session Management - it is used by Developer coded callback methods…
Transaction Management - it is used by configuring deployment descriptor (DD) .
Security management - it is used by configuring deployment descriptor (DD) .
The other services, if any will be in advanced versions, and depends on Vendor specific.

1.An MDB is essentially a message consumer that can listen to a message destination or a message endpoint and GETS activated when a message arrives.
2.By DESIGN, MDBS are anonymous in nature and hence cannot be directly invoked by a client.
3.The only way to invoke an MDB is to send a message to the destination or endpoint to which it is listening.
4. As MDBs are STATELESS in nature and are not related to any specific client, they can be pooled for concurrent processing of messages.

1.An MDB is essentially a message consumer that can listen to a message destination or a message endpoint and gets activated when a message arrives.
2.By design, MDBs are anonymous in nature and hence cannot be directly invoked by a client.
3.The only way to invoke an MDB is to send a message to the destination or endpoint to which it is listening.
4. As MDBs are stateless in nature and are not related to any specific client, they can be pooled for concurrent processing of messages.

Following are some of the main FEATURES SUPPORTED in EJB 2.0:
1. Integration of EJB with JMS.
2. Message Driven Beans.
3. Implement additional BUSINESS METHODS in Home interface which are not SPECIFIC for bean instance, EJB QL.

Following are some of the main features supported in EJB 2.0:
1. Integration of EJB with JMS.
2. Message Driven Beans.
3. Implement additional Business methods in Home interface which are not specific for bean instance, EJB QL.