Forums.Sureshkumar.net : A Perfect Place to Share Knowledge         Blogs     Games    Magazines    

"Sharing knowledge does not lessen your store, often it gets you more. Sharing plays a key role in relationships and bonding, happens in small steps and is assisted through community membership."

Go Back   SURESHKUMAR.NET FORUMS > TECHNICAL DISCUSSIONS > JAVA Technologies
Register FAQ Members List Calendar Games Blogs Search Today's Posts Mark Forums Read

   

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
Old 05-11-07, 11:01 AM   #1 (permalink)
Senior Member
 
Join Date: Aug 2006
Age: 28
Posts: 275
Thanks: 0
Thanked 5 Times in 5 Posts
Thanks: 0
Thanked 5 Times in 5 Posts
Rep Power: 5 radhika743 is on a distinguished road
EJB: How container will maintain synchronization of multiple calls to an entity bean?

How the container will maintain synchronization for multiple calls to the entity bean?

Is it by transactions? Is so , what is the default transaction attribute setting to entity beans?

Can someone please clarify this for me?
radhika743 is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Old 06-11-07, 04:29 PM   #2 (permalink)
Banned
 
Join Date: Sep 2007
Age: 25
Posts: 88
Thanks: 0
Thanked 4 Times in 4 Posts
Thanks: 0
Thanked 4 Times in 4 Posts
Rep Power: 0 satya5321 is on a distinguished road
Re: EJB: How container will maintain synchronization of multiple calls to an entity bean?

Container maintains a pool of entity beans in order to satisfy the mulitple client requests.
satya5321 is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Old 12-11-07, 12:11 PM   #3 (permalink)
Banned
 
Join Date: Sep 2007
Age: 25
Posts: 88
Thanks: 0
Thanked 4 Times in 4 Posts
Thanks: 0
Thanked 4 Times in 4 Posts
Rep Power: 0 satya5321 is on a distinguished road
Re: EJB: How container will maintain synchronization of multiple calls to an entity bean?

in case of Entity beans once the client request is completed. It comes to Instance pool to satisfy next client.Here container maintains a pool of Entity Bean instances to satisfy multiple client requests.
Stateful Session Beans are dedicated to one client.
Once a stateless session bean has finished a method invocation for a client, it can be reassigend to any other EJB object to service a new client.
satya5321 is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Old 31-03-08, 05:51 PM   #4 (permalink)
Member
 
Join Date: Mar 2008
Posts: 32
Thanks: 0
Thanked 0 Times in 0 Posts
Thanks: 0
Thanked 0 Times in 0 Posts
Rep Power: 1 writetokaruna@yahoo.com is on a distinguished road
Re: EJB: How container will maintain synchronization of multiple calls to an entity bean?

It is a nice answer.

EJB container itself takes care of synchronization task.so single instance can respond for more than one request simultaneously.


Comments are welcome.

Regards,

R.P.Karunakaran.
writetokaruna@yahoo.com is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
J2EE - What is Entity Bean and types preethisingh Java Interview / Technical Questions 1 23-01-07 08:17 PM
J2EE - Why the container does not support multiple layout managers preethisingh Java Interview / Technical Questions 0 23-01-07 02:03 PM
ENTITY BEAN QUESTION? radhika743 JAVA Technologies 1 02-01-07 11:47 AM
Java Contest-13 with answers keerthi JAVA Technologies 8 31-12-06 09:44 AM


All times are GMT +6.5. The time now is 02:56 AM.





Search Engine Optimization by vBSEO 3.1.0