Win a copy of Java Concurrency Live Lessons this week in the Threads forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

EJBs as an interface  RSS feed

 
Sanjay Anand
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In an earlier discussion [http://www.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=11&t=002344], Tim Holloway suggested that:
One possible resolution to that might be to use the EJBs as an interface and have them defer to a common resource, though that's really just pushing the problem a layer deeper.

Tim was addressing the problem of 'version creep' versus synchronization of business logic across multiple apps.
But we are considering this as a standard since it fits our general model of code management to have a centralized location for all business logic.
How viable is this solution? Does this create any performance or deployment issues? Or does it violate any fundamental J2EE guideline?
I would appreciate any feedback you could give me.
Thank you
Sanjay
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!