Section 20.3 of the PFD2 and final PFD3 specs talks about the use of logical names to refer to home objects of other beans. I don't see anything in there about relationships and packaging.
I assume you are referring to container managed relationships which are described in section 10 (e.g. 10.3.2 and 10.4.2 seemed helpful). Since CMR now relies on local interfaces, there is a requirement that the local client be collocated in the same JVM (see Section 5.3). I can't find any direct requirements in the spec that require that they be collocated in the same jar but it is simpler because each local client needs access to the classes of the local interface. -Chris Thompson Bean-test Developer http://www.empirix.com -----Original Message----- From: Duncan Alexander [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 1:20 PM Subject: Re: Setting EJB Specific Classes in a Client VM With reference to that article in ONJAVA and the statement below: <extract> ...PFD1 allowed EJBs in different JAR files to participate in relationships, further promoting greater modularity of the system, but ultimately limited the persistence optimizations that containers could do for CMP entity beans in a relationship. Now that PFD2 eliminates this capability, many vendors are providing tools that perform EJB JAR convergence... </extract> I understood from the EJB 2.0 Specification(PFD2) section 20.3 that EJBs could participate in relationships with other EJBs in different jars as long as they used the ejb-link element within the ejb-ref tag in the deployment descriptor. Would that not make the above reference incorrect...anyone? regards DGA -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Rickard Sent: 14 February 2002 17:14 To: [EMAIL PROTECTED] Subject: Re: [EJB-INT] Setting EJB Specific Classes in a Client VM Mike Dunbar wrote: > I have a related question, which I plan to consult documentation/specs > for. In the meantime, maybe someone could answer both of these at the > same time. My question is: > > I want to deploy a .ear file that contains some EJB .jar files along > with a .war file. The .war file will contain classes that are clients > of the EJBs in the .jar files. This is a common thing, I am sure. Do I > need any of the EJB stubs, etc. in the .war file? Does it vary from app > server to app server? If so, what do the associated specs say about > this? http://www.onjava.com/pub/a/onjava/2001/06/26/ejb.html -- Rickard �berg Author of "Mastering RMI" Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! ======================================================================== === 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".
