EJB Design Question

I am not sure about how many rules this design may break but the truth is
it may be really a bad design if mixing data from multiple business application
in the same data source is a problem for you. Maybe you should set up multiple
data sources for your EJB and use them by checking which business application
is the caller. I am sure you can find a good solution for that following
a pure OO methodology.

Hope that helps,

Fernando Ribeiro
fribeiro

"Chad" <chad.kottmann@citicorp.com> wrote:
>
>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
>database.
>
>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.
>
>Thanks
>Chad