Hi all
Thanks for the reply. I was actually talking about one Jar per package. I have
only one developer working on a particular package. So, I will not get into
development related problems. Also, I have a source control system to take care
of other logistics.
In all packages I have a session bean and multiple entity beans. All EJBs now go
into the same Jar file. Now if a particular entity say Entity1 in this package
is used widely and I want to more this entity to another app server, it would be
easiser if I had this entity in a separate Jar. In the current scheme, where all
EJBs in the same java package go into same Jar file, I would not be able to
easily deploy a particular set of beans in another server. Although I have not
practically tried this stunt myself, I thought this could be the case ..
Regards.
--
shiv
[EMAIL PROTECTED]
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
===========================================================================
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".
