kenji,
Most ejb vendors provide some mechanism of
'hot deploy' for their products.
This is (as far as i am aware of) completely vendor
specific. For some vendors, it involves just dropping
a jar file into a directory, while for others it involves
using vendor provided deploy utilities (command line
and/or gui tools).
This realm is outside the ejb specification. There is
no 'common programmatic interface' that works
for any _two_ ejb vendors - let alone 'nearly all'
containers. :)
-krish
----- Original Message -----
From: Kenji Konaka <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 13, 2001 1:44 PM
Subject: dynamically define/deploy a bean (?)
> hi!
>
> if I were to dynamically generate code (ie., some .class files for
> home/remote/bean,etc.; maybe by way of a program running externally to
> the container), and to deploy it on the fly while the container is
> running; what would be the concerns I would probably like to watch out
> for?
> - is there any tricky consequences regarding the security?
> - is there any common programmatic interface which works for (nearly) all containers?
> - anything else?
>
> ;; please excuse if this was a sort of newbie question...
> kenji
>
> ===========================================================================
> 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".
