That seems to mean that we will be without an effective method of product
integration for at least another year (judging by the length is has taken
the PFD2 to get where it is and the length of time it will take vendors to
catch up with the spec). Kinda makes working with components and packages
of components quite difficult. Which leads to the following:
a. Since relationships cannot be used across multiple ejb-jar.xml files
b. And without relationships ejb-ql is quite useless since it depends on
relationships for navigation
c. And without ejb-ql CMP becomes quite useless since you cannot express
your finders (similar to the 1.1 spec days)
d. Then why use relationships or CMP at all, it's a great tool but you will
quickly hit a limitation, unless you are developing a monolithic system
where all the beans are deployed in a single ejb-jar.xml?
Then the only thing EJB 2.0 spec really gives us is message driven beans?
Seems like a lot of work, for such minor functionality.
I think remote relationships need to be finalized in EJB 2.0 spec, to make
the transformation complete. With remote relationships removed from current
EJB 2.0 spec, I am concerned that we will remain in the 1.1 world with
having to do our own BMP, or be locked in to some vendor's proprietary
implementation of this missing functionality.
They should put remote relationships back into the spec, and deprecate it
later, when a better solution can be reached. At least, there would be a
way to "relate" between multiple deployment units (in the same server).
-AP_
PS: I hope someone can correct me on this issue. Perhaps I am missing
something in the spec.
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Evan Ireland
Sent: Sunday, April 29, 2001 10:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Serious integration problems with PFD2
Alex,
I share your concern.
We hope that 'remote' relationships will be supported in a future
EJB spec revision.
Alex Paransky 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
>
> -AP_
> www: http://www.standardset.com
> resume: http://www.standardset.com/resume_body.jsp
> home: (818) 541-0029
>
>
===========================================================================
> 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".
--
____________________________________________________________________________
____
Evan Ireland Sybase EAServer Engineering
[EMAIL PROTECTED]
Wellington, New Zealand +64 4
934-5856
===========================================================================
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".
