EJB Design Question
The development group that I work in is new to using EJB
technology and we have come up with a design question.
Suppose I create an Entity Bean (call it "widget") that can be
reusable among several business applications. Would it be the
accepted standard to deploy the Widget EJB to a single application
server, having the Widget EJB store it's Widget data to a single
If the Widget EJB is utilized by multiple Business Apps,
eventually that EJB's datastorage mechanism will contain
Widget data from several different business apps. Is this
the accepted design? Has eanyone had problems doing this?
(especially with perfomrance, with data integrity,
or with simply making several applications vulnerable to
problems with a single component?)
If anyone can relate their experiences or views on this matter it
would be greatly appreciated.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL