On Tue, 2003-02-18 at 11:42, Noel J. Bergman wrote: > > Though mailet.jar exists in the /lib > > The mailet.jar is built during the build process, and is not located in > lib/. If you see mailet.jar in lib/, you are looking in the wrong directory > (build/lib/). > > -- run ./build.sh clean (or build clean) > -- put your jar in lib/ > -- do the build > > To recap: you have a mailet in org.apache.james.transport.mailets, and it > relies upon a third party jar. The mailet should be built along with james, > and the third party jar in lib/ prior to doing the build, along with the > rest of the third party jar files.
I have a mailet in say: home.application.myMailets and it imports third party classes. Initially I used to place my jar file containing the myMailet jar and third party jar in build/lib and then re-build. Now when I place them in lib and re-build, it says: Could not load mailet (myMailet) I have put the right package in mailetPackages in the conf file. Do we need to load the third party classes that the custom mailet uses by using the classLoader the way mailet loader does it? maybe overwrite the init() method of mailet. This is the only thing I can figure out why it overlooks the third party classes. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Disha <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
