Understood, but just because the J2EE spec does not provide an explicit way of handling this situation does not mean that it will not in the future. The fact is that many applications that are dynamic in nature require a mechanism for loading in classes dynamically. J2EE as a whole seems to be very static by nature. Meaning that once you deploy a application it seems difficult as an AppVendor to provide a platform independent way of extending the application.
With that said, we are resistant to tying into any one Application Server. But if there is functionality, that is not part of the spec, but provided by the Major Application Servers we will simply write a wrapper for each. Let me re-iterate though, that we have been very pleased with J2EE1.3. The part of our application that requires classloading, although important, is a small piece of the application. And I am confident that we will find a work-around, especially with the great feedback I have gotten from this list. Thanks again, Shone -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Sacha Labourey Sent: Monday, January 14, 2002 7:08 AM To: [EMAIL PROTECTED] Subject: Re: EJB & ClassLoading ... > 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. OK, but you have to understand (and I am sure you already do) that what you are "complaining" about is app-server specific and even in some cases, at the very heart of the server: classloading. To make some kind of analogy, it is like if you said "I don't like the way the OS thread scheduling work, so I want to replace it and I want my app to work on linux, solaris and windows xp." Unless you do os-specific implementation of some parts, you will have trouble. Cheers, Sacha =========================================================================== 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".
