Hi, This commit marks the first step towards the mailet deployment/classloading goals set out on the wiki. Unfortunately formatting changes got caught up with the code changes, sorry.
It doesn't achieve much more than prove that I have my head round the lifecycle of mailets and matchers. I've run some tests on it, and it _appears_ to work as advertised and without breaking anything. In a nutshell you can now put mailets and matchers and their dependancies into ~/apps/james/SAR-INF/classes or in jars in ~/apps/james/SAR-INF/lib. I don't know if it would be a desirable addition to 2.2 or not, from the POV of stability, but I know its something folks've wanted for quite a while. Next step is to seperate the mailet classloader from James to hide non API classes not explicitly installed for mailets. I know I'll have to make an exception for the current db-access mailets until we do something to make them compliant. d. > danny 2003/01/08 04:31:05 > > Modified: src/java/org/apache/james/transport JamesSpoolManager.java > MailetLoader.java MatchLoader.java > Log: > Mailet Classloader changes. First efforts.. > Mailet and matcher classes and their dependancies can now be loaded > from ~/apps/james/SAR-INF/classes > and jars in ~/apps/james/SAR-INF/lib/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
