It looks like you're right, which (looking at our typical deployment
organization) makes the spec completely unsuable in that regard. could you
crosspost your email to EJB-INTEREST? It's more likely that you'll get a
response from an expert group member. I sure hope we're both missing something.
Regards,
Robert
At 14:38 27.04.2001 , you wrote:
>Looking at the latest spec PFD2, it appears that it is not possible to
>establish a unidirectional relationship between two entity beans in separate
>ejb-jar.xml files. With the removal of remote-ejb-name as a possible value
>for <role-souce> it makes integration of two packages impossible without the
>mess of taking and trying to merge two ejb-jar files into one.
>
>Scenario 1:
>We are developing an general accounting package. Our clients need to
>integrate with our package by establishing uni-directional relationships
>from their CMP Entities into what we provide them. Since they will not be
>altering our ejb-jar (except for deployment) how can they reference our
>beans?
>
>Scenario 2:
>Our accounting package contains a good number of CMP Entity beans. Since
>EJB A relates to B, and B relates to C, and C relates to D and E, and E
>relates to G and so on. It is not possible to separate the ejb-jar into
>multiple, smaller, ejb-jar files for the purpose of managing and controlling
>change. With over 100 EJBs a single ejb-jar becomes very unmanageable.
>
>Are there any solutions to these problems?
>
>Thanks.
>Alex Paransky
>Individualnetwork.com
>
(-) 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
