tinou,
on the contrary, i would recommend (other opinions?)
grouping EJBs into packages based on functionality of
your application domain rather than anything else. that
is entire point of package names - is it not? of course
you might append a "session" or "entity" package at
the very end if you so prefer - but much of it is upto
you - the bean provider.
and of course it should make life easier for the developers
in your team as well other teams.
-krish
----- 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".
