> Exactly right Ted, you explained it much better than me. But that is > exactly the functionality > we are looking for. We need to explicitly manage the classloading and be > able to associate a classloader with each > component so they can each have their own namespace. Implementing each > component as a SSB would work if we had the capability of managing the > deployment ourselves, because there is more to our component than the > business logic that would be implemented in the SSB (Dialog, meta-data, > etc...). Furthermore we require that the deployment is dynamic and can be > done without bringing the system down. Thanks to you and Sacha we have a > few JSRs to look at.
<AppServerSpecific> Then you may take a look at JBoss 3.0 features. It will provide very flexible classloading, such as hot-deployement, undeployement, redeployement of beans AND services with dependencies tracking, ... It will even provide cluster-wide hot-deployement features. You may then use your J2EE infrastructure inside it and use available features to manage what you need. Currently, JBoss 3.0 is only available in alpha but a beta should follow quickly. </AppServerSpecific> =========================================================================== 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".
