Hello everyone, We have recently converted our app to take full advantage of J2EE1.3. There is one part of our application that relies heavily on classloading. In particular, We load up a component (which is written to our specification) from the database. The component contains an xml descriptor and may contain external libraries as well. Unfortunately, the J2EE specification still prohibits classloading. Has anyone done anything similar? The three approaches we are looking at doing include:
1. Simply leave the classloading in the EJB Bean (Stateless Session Bean). And test on various AppServers. 2. Implement an RMI server that does the class loading and call it from our Bean. 3. Implement our components as Stateless Session Beans, so that the EJB Container handles the class loading. To us option 3 seems the most appealing, but there some issues with deployment. It is a requirement for our application to be able to dynamically add new components and redeploy existing one without bringing the system down. Furthermore, our components include more than the execution service they also include a Dialog, etc.. used by other parts of the application. We currently have a UI for deploying our components, the system would need to deploy a component to any Application Server when a deployment is made to the database through the UI. This requires the Application Server to support Hot Deployment and preferably provide a Deployment API. Any feedback about a better alternative would be appreciated! Thanks, Shone =========================================================================== 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".
