Hi,
Could you try using the full classname (with the package) in you
mailetcontainer.xml? Putting the jar with all its dependencies in
<james-home>/conf/lib should work.
Btw, documentation is updated but still needs to be deployed.
Thx.
On 18/07/11 23:59, Charley Watson wrote:
Howdy,
I'm running a James 3.0 M2 build on Redhat--
I've read a number of articles on deploying custom mailets to 3.0 instances--none of
them use a standard method to discover the<my-custom-mailet>.jar.. Is there a
prescribed method?
Here's the symptoms I'm experiencing..
Invoking<james-home>/bin/james start
mailetcontainer.log shows the matcher before<my-custom-mailet> being loaded;
then a server failure logs a shutdown.
Invoking<james-home>/bin/james console (I get better logging this way)
The wrapper logging shows the "Requested mailet not found:<my-custom-mailet>"
The spring context appears to be eager loading so I expect that something is
wrong with my deployment classpath and the discovery order.
A) jar is deployed to<james-home>/lib
B) CLASSPATH_PREFIX is set to include<path-to-my-custom-mailet>.jar
in<james-home>/bin/setenv.sh
I have also tried
A) Deploying to<james-home>/conf/lib (with and without the CLASSPATH_PREFIX).
The docs on deploying a custom mailet appear to be out-of-date as they include
references to sar files which appears to be 2.3 legacy kruft.
Any knowledge pointers to working examples of custom-mailets greatly
appreciated.
Thanks for any help,
CW
Charley Watson
Systems Engineer
--
Eric Charles
http://about.echarles.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
