[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-user
Subject:    Re: Deploying Custom Mailets
From:       Norman Maurer <norman () apache ! org>
Date:       2011-07-20 6:18:27
Message-ID: 4E267333.9020504 () apache ! org
[Download RAW message or body]

Hi there,

comments inside...

Am 19.07.2011 20:40, schrieb Charley Watson:
> Eric,
> 
> Thanks for the tip... The fully qualified class name trick works...
> 
> Q1: Is this a bug or by design?  My mailetcontainer.xml has a package space \
> matching my mailet in the mailet-packages element.

Its by design. We only allow to use the classname in the mailets which 
ship with James. This was changed to be sure we don't get any name 
clashes and also to make sure we can support OSGI in a cleaner way later.


> 
> Q2: What dependencies are guaranteed for mailets in the out-of-the-box \
> configuration for James?  I added the following but don't know if they comply with \
> the deployment scheme and class discovery employed by James: 
> <james-home>/conf/lib/apache-mailet-2.4.jar
> <james-home>/conf/lib/james-stuff-0.0.1-SNAPSHOT.jar (my customizations)
> <james-home>/conf/lib/mail-1.4.3.jar (depended on by apache-mailet)
> <james-home>/conf/lib/mailet-3.0.jar (depended on by my custom binary)

This stuff is guaranteered to work also on other mailet container 
implementations (I don't think there is an other then james atm). When 
running in James you can access a lot more. You can use @Resource(..) 
annotations to inject every service which is declared. So its really a 
lot more..

So you should be able to use every "-api*" jar too.

> 
> Seems like some of these 'extra' deployments might cause security exceptions when \
> encountered by classloaders...

Don't get your point here.. Can you give some more details ?

> 
> My custom code extends GenericMailet following an example in the docs--if there is \
> a better preferred method to implement mailets that help would be appreciated.

GenericMailet is the way to go..

> 
> Thanks,
> 
> Charley Watson
> Systems Engineer
> 
> -----Original Message-----
> From: Eric Charles [mailto:eric@apache.org]
> Sent: Monday, July 18, 2011 9:54 PM
> To: James Users List
> Subject: Re: Deploying Custom Mailets
> 
> 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
> > 
> > 
> > 
> > 
> > 


Bye,
Norman


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]