Skip to Content Sun Java Solaris Communities My SDN Account Join SDN

Developers Home > Products & Technologies > Java Technology > J2EE > EJB > Learning > Quizzes >

Quizzes

Applying Enterprise JavaBeans, Second Edition

Print-friendly Version

Quizzes Index

By Vlada Matena, Sanjeev Krishnan, Linda DeMichiel, Beth Stearns
January 2004

This quiz is based on the book Applying Enterprise JavaBeans, Second Edition, an advanced programming guide to the Enterprise JavaBeans 2.1 architecture. Test your knowledge of the latest EJB architecture features.

Choose the best answer(s) for each question, then click Submit to see how you scored.

Learn more about Enterprise JavaBeans, download the J2EE 1.4 SDK.

Both session and entity beans can implement local and remote client views, and generally the same considerations apply. However, an entity bean must implement a local client view in what situation?

A.	When the application uses message-driven beans.
B.	When the entity bean is a target of a container-managed relationship.
C.	When the entity bean is located in a different JVM from the client.
D.	When the application uses a session bean as a facade to a set of entity beans.

The EJB 2.1 architecture includes an SQL-like query language, EJB Query Language (EJB QL), that is portable across EJB containers. This language can be used to express queries for

A. Message-driven beans

B. Session beans implementing remote client views

C. Entity beans with container-managed persistence

D. Stateless session beans
An EJB application may use message-driven bean components to asynchronously receive messages provided that the messages are delivered by which message service:

A. Java Message Service (JMS)

B. Java API for XML Messaging (JAX-M)

C. Any other messaging system

D. JMS, JAX-M, or any other messaging system

E. None of the above
Implementing a message-driven bean requires that the developer extend two interfaces: a message listener interface and

A. a javax.ejb.SessionBean interface

B. a javax.ebj.MessageDrivenBean interface

C. an event listener interface

D. a javax.ebj.EJBHome interface
A message-driven bean developed for a JMS messaging system puts its business processing logic within which method:

A. setSessionContext method

B. onMessage method

C. ejbRemove method

D. setMessageDrivenContext method

E. a user-defined method
If you use container-managed transaction demarcation, you can set a message-driven bean to participate in a transaction. To ensure that message delivery from the message destination to the message-driven bean is part of the subsequent transactional work, set the message-driven bean's transaction attribute (in the deployment descriptor) to

A. NotSupported

B. Mandatory

C. Required

D. Supports
The EJB timer service is used for timing notifications. It can be used with

A. CMP entity beans

B. both BMP and CMP entity beans

C. message-driven beans

D. B and C

E. A and C

F. None of the above
EJB Timer objects are stateless objects, with the same characteristics as stateless session beans.

A. True

B. False
An enterprise bean may set up a timer notification using the TimerService's createTimer method. Such timer notification may occur

A. After a specified duration

B. At a specified time

C. On a recurring basis

D. All of the above

E. None of the above

The J2EE 1.4 platform includes a set of Web services technologies for developing Web services applications. Developers can use the following technologies to write a Web service Java interface or service endpoint interface:

A.	Java API for XML Processing (JAX-P) and Java API for XML Binding (JAX-B)
B.	SOAP with Attachments API for Java (SAAJ)
C.	Java API for XML-based RPC (JAX-RPC) and enterprise bean components
D.	Java API for XML Registries (JAX-R)

To develop a Java interface for a Web service-the service endpoint interface-you must start with the WSDL (Web Services Description Language) document for the service.

A. True

B. False
Which type of enterprise bean is particularly well suited for developing a JAX-RPC service endpoint interface for a Web service?

A. A messaged-driven bean

B. An entity bean

C. A stateless session bean

D. A Timer object

E. A stateful session bean

When developing an enterprise bean as a JAX-RPC service endpoint interface for a Web service, you must adhere to the following rule:

A.	The bean must not extend java.rmi.Remote nor should its methods throw java.rmi.RemoteException
B.	The bean's methods must use remote reference types
C.	Deploy the bean using a special Web services deployment descriptor, webservices.xml.
D.	None of the above.

Enterprise beans can be used to access Web services. To do so, the bean must:

A.	Declare a service-ref element in its deployment descriptor that contains appropriate information to look up the Web service endpoint.
B.	Package the Web service endpoint into an ejb-jar file.
C.	Create a webservices.xml file containing the Web service.
D.	Include a JAX-RPC handler in its code.

For a new Web service developed using enterprise beans, you must package its components into an ejb-jar file. Which of the following are not packaged into the ejb-jar file:

A.	All classes referenced from the bean class and the interface
B.	The WSDL file
C.	The deployment descriptor for the Web service
D.	The stubs, skeletons, and serialization/deserialization code for translating SOAP requests to invocations on the bean class.


	About Sun \| About This Site \| Newsletters \| Contact Us \| Employment How to Buy \| Licensing \| Terms of Use \| Privacy \| Trademarks Copyright Sun Microsystems, Inc.		A Sun Developer Network Site Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License. Sun Developer RSS Feeds