Tech Grill - Where Ideas Sizzle

 
About Me

Enter your email address:

Free updates in your email
Google
Web techgrill
Top Articles

Celebrate your freedom to read

Cache it out - Keep your PC Sparkling clean

Get Classic ebooks for Free

Gmail - email ID naming tips

Google to find Passwords

Use Notepad as a Diary

Five Orkut Tips and Tricks for Beginners (Part1)

Orkut Tips & Tricks (Part 2)

Boost up your Firefox Browser

Book Reviews
Links
Powered by

Free Blogger Templates

BLOGGER

Technorati
Frequently Asked EJB Interview Questions (Part 2)
Tuesday, September 19, 2006
Is it possible to stop the execution of a method before completion in a SessionBean?
Stopping the execution of a method inside a Session Bean is not possible without writing code inside the Session Bean. This is because you are not allowed to access Threads inside an EJB.

What is the default transaction attribute for an EJB?
There is no default transaction attribute for an EJB. Section 11.5 of EJB v1.1 spec says that the deployer must specify a value for the transaction attribute for those methods having container
managed transaction. In WebLogic, the default transaction attribute for EJB is SUPPORTS.

What is the difference between session and entity beans? When should I use one or the other?
An entity bean represents persistent global data from the database; a session bean represents transient user-specific data that will die when the user disconnects (ends his session). Generally, the session beans implement business methods (e.g. Bank.transferFunds) that call entity beans (e.g. Account.deposit, Account.withdraw)

Is there any default cache management system with Entity beans ?
In other words whether a cache of the data in database will be maintained in EJB ?
Caching data from a database inside the Application Server are what Entity EJB’s are used for.The ejbLoad() and ejbStore() methods are used to synchronize the Entity Bean state with the persistent storage(database). Transactions also play an important role in this scenario. If data is removed from the database, via an external application - your Entity Bean can still be “alive” the EJB container. When the transaction commits, ejbStore() is called and the row will not be found, and the transaction rolled back.

Why is ejbFindByPrimaryKey mandatory?
An Entity Bean represents persistent data that is stored outside of the EJB Container/Server. The ejbFindByPrimaryKey is a method used to locate and load an Entity Bean into the container, similar to a SELECT statement in SQL. By making this method mandatory, the client programmer can be assured that if they have the primary key of the Entity Bean, then they can retrieve the bean without having to create a new bean each time - which would mean creating duplications of persistent data and break the integrity of EJB.


Keywords : Java, Enterprise Java Beans, EJB, Java Enterprise Questions, Technical Questions for Interview
posted by Administrator @ 4:35 AM  
0 Comments:
Post a Comment
<< Home
 
Sponsored Ads
Previous Post
Archives
© 2005 Tech Grill - Where Ideas Sizzle Template by Isnaini Dot Com