anish, with EJB 2.0 you'll have to put them into one jar. check the archives for a thread called 'EJB 2.0 final - what we have to live with now' (http://swjscmail1.java.sun.com/cgi-bin/wa?A2=ind0109&L=ejb-interest&P=R25481&m=11650) for a discussion of this issue (among others). I'm very unhappy with this restriction but other people argue that the deployment units (ejb-jars) should be more clearly separated than inter-ejb-jar relationships. IMHO the result of this is either lots of unnecessary extra coding to implement the relationship yourself or huge jars which causes a bad hit on development cycle efficiency.
hope this helps, robert On Wednesday 28 November 2001 17:25, you wrote: > We are in the process of deciding our packaging and we seem to have run > into a dilemma. > > I have say 3 entity beans..Bean A, Bean B, Bean C. > > Now bean A has a relationship to Bean B > > Bean B has a relationship to Bean C > > My Question > > Do I have to put all the beans in one jar file ? > > OR > > Can I separate the beans in separate Jar files and still have the > relationship working ? > > Thanks for your feedback > > Anish =========================================================================== 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".
