Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Keeping EJB as Client ?

 
vikasids sharma
Ranch Hand
Posts: 157
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi all
My ejb client calls for a session bean. Now i want this session bean to call some entity bean which resides at different application server.
Please let me know which out of two options is better and why?
1. I make this session bean as client for entity bean existing at diiferent server and calls it using JNDI.
2. I make a call to session bean and on the basis of what it returns makes call to another session bean(this session bean further calls entity bean)existing at different application server from same client code.
thanks
Vikas
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'd vote for option 1.
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Definitely go with number 1. The client shouldn't need to know all the gory details...
 
Naveen Sharma
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Go with a clean approach ... No. 1
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic