• Post Reply Bookmark Topic Watch Topic
  • New Topic

is serverLocator pattern need if EJB is local machine?

 
Kaleeswaran Karuppusamy
Ranch Hand
Posts: 155
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i like to know whether the serviceLocator pattern is needed if the EJB deployed in local machine.
 
Bill Shirley
Ranch Hand
Posts: 457
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
serviceLocater (as stated in the question, not serverLocator as stated in the title)

is a design pattern that is basically a JNDI abstraction,

(generally) no design pattern is ever required, and this one is of benefit when your service's location is known to change, if you know it won't then it's of less value,

(of course, bosses and clients always like to change requirements mid-stream/late in the game, so the more abstractions the better)

that particular collection of design patterns was created to solve the implementation requirements of EJB 1 and 2 (as witnessed by their 2002 copyright) - many of the issues they solved have been re-solved by the re-design of EJB 3. I recommend understanding the problem each of them is trying to solve before using them.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!