We have been using JBOSS for development internally and it has been great. But a goal of ours has been to right to the J2EE specification and not use any proprietary tool sets or APIs provided by the AppServer. There are many reasons for which, but not the least of which is that our customers expect it. We have customers using Weblogic, Websphere, JRun, etc...
As a result, instead of using frameworks provided be the App Server vendors we have been developing our own frameworks ontop of the J2EE specification including O/R mapping, MVC framework for both web and fat clients, etc.. In addition to portability, this gives us the flexibility for implementing functionality not available in current App Servers. Shone Sadler -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Sacha Labourey Sent: Monday, January 14, 2002 3:52 AM To: [EMAIL PROTECTED] Subject: Re: EJB & ClassLoading > 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". =========================================================================== 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".
