I read somewhere EJB 2.0 spec highly recommends packaging all beans that
have relationship to one another into one package, especially to take
advantage of Local Interfaces. This is somewhat akin to current
optimization of some vendors that do pass-by-reference, but only if the
beans exist in one package.
Gene
----- Original Message -----
From: "Tinou Bao" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 3:24 PM
Subject: each ejb having its own package
> what are people's options of this? is it practical for large projects with
> lots of ejbs? examples always have each ejb in it's own package, as does
the
> blueprint petstore example. i can see how it maybe easier for packaging
into
> jar files and building, but at some point doesn't it become cumbersome to
> have so many packages.
>
> thanks.
===========================================================================
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".
