At 09:39 14.11.00 , you wrote:
>Hi there,
>
> > Ok. But only one DS per deployed bean?
>
>No, I have one DS per instance but more possible DS per deployed bean.
how do you ensure uniqueness of the entities then? an entity pk is required
to be unique within the scope of the same home (i.e. per deployed bean).
otherwise caching, transaction mgt etc. of the conainer would not be able
to work properly because it relies on that (see EJB2.0 spec section 8.5).
if I understand correctly what you're trying to do, I'd reconsider the
design. it looks like it gets pretty messy and it's not what you really
want to do and how entity beans were meant to use. deploying one of you
generic table access beans (that's what you're trying to do right?) per
table and datasource should be the way to go.
regards,
robert
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
