Remy Maucherat wrote:
Costin Manolache wrote:
In JBoss, the default is to use the JBoss loader. Is there any big difference ?Remy Maucherat wrote:
Costin Manolache wrote:
Quick question - did you had any discussion on class loaders for 5.next?I'll tweak the StandardCL to do a bit the same as the WebappCL (ie, try to make it faster). I'll also remove the anti locking hacks which are in WebappCL.
It's one area I'm playing with, I want to make sure I'm not going in oposite direction :-)
Ok. I'm experimenting with having tomcat use other class loaders ( for example if embedded in another app, or used with a different runtime - like eclipse OSGI ).
Both difference and similarity :-).
Eclipse ( osgi actually ) has a similar flat loader implementation, but with finer control over what is exported/imported and pretty strong versioning. In addition osgi supports permissions on importing packages.
The reloading of modules is a bit more complicated than in jboss ( where you just change the jar ).
From tomcat point of view - the implementation should be very similar with jboss.
What I like is the standardized and simpler behavior of class loaders, with ability to reload and upgrade any module ( like jboss ).
Don't know what "dependency injection" is, but I hope the next spec won't invent yet another way to do configuration.Sorry for using hype words. I got contaminated, it can happen to anyone. I'll try to shake it off now. I apologise to the community for that, and I won't do it again (hopefully) ;)
Well, when I see a buzz word I don't know I try to search it - and what I found on dependency injection is scary ( i.e. avalon and friends ).
Costin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]