How do you avoid restarting the Inprise Application Server/EJB Container when you redeploy an existing EJB jar?
| How do you avoid restarting the Inprise Application Server/EJB Container when you redeploy an existing EJB jar? |
|
Out-of-process is not a problem: use the Console's deployment wizard. Or, if you have local jar files, use the com.inprise.ejb.util.Deploy utility described in the FAQs to unload/load/reload EJB jar(s). In-process: you must restart the container (server if classpath changes) or change to an out-of-process container.
|
Article originally contributed by Borland Developer Support