Hi again, I'm studying the ejb 2.0 many2many account-customers example in
weblogic 6. and it still looks like the developer still has the
responsbility to define the correlation via a relationship definition from
customer and account so the container certainly doesn't name it's own table.
However I am keen to know how this is handled when you have attributes in
your relationship. So when you have no additional relationship an entity
bean mapped to your correlation entity isn't necessary...
So presumably this approach forces you to have a composite key for your
correlation table instead of a unique object identifier in addition to the
two foreign keys as attributes in this table in order to have the same
primary key fields across all your tables. CMP forces you to use semantic
keys this way. I've worked on projects where object-id's were used even for
correlation entities. It seemed to make sense and made everything
consistent.
In Weblogic do you have to define the contents of
weblogic-cmp-rdbms-jar.xml by hand?
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Hemant Khandelwal
> Sent: Sunday, March 11, 2001 8:50 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Modelling many to many relationships with EJB 2.0 compliant
> containers?
>
>
> Hi Robert,
>
> The conatiner and Persistence Manager will tranparently manage the
> relationship.
>
> But there is an instance when an entity ejb needs to be defined for
> correlation entity. The case is when there are attributes of the relation.
> (Please check the archives for a previous discussion on the same thread.)
>
> Hemant
> www.pramati.com
>
> ----- Original Message -----
> From: "Robert Nicholson" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, March 12, 2001 8:42 AM
> Subject: Modelling many to many relationships with EJB 2.0 compliant
> containers?
>
>
> With the CMP offered by EJB 2.0 compliant containers. Is the correlation
> table completely transparently managed by the container?
>
> That is. Do I have to have an entity ejb for the correlation entity and
> .create it when I wish to create the assocation? Or can I do
> everything via
> references from the to one side of the relationship's entity? via. addXXX
> methods?
>
> Same question applies to EJB 1.1 containers too. How exposed is
> the "client"
> to the correlation table?
>
> ==================================================================
> =========
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
> ==================================================================
> =========
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
