More information: based on a text search in the code base, it looks like at
least the standard mailet classes are being found because the standard
mailets package is being specified via java code rather than in an xml
configuration file. That code is in
org.apache.james.container.spring.bean.factory.mailetcontainer.MailetLoaderBeanFactory.java:
@Override
protected String getStandardPackage() {
return "org.apache.james.transport.mailets";
}
Now I guess I should try directly using a custom mailet by specifying its
fully qualified name in conf/mailetcontainer.xml. If that works fine it
would be good enough for me. I do remember thinking it was not that elegant
to have to specify a package separately so if this is a recent change and it
works I'm more than happy.
On Wed, Feb 9, 2011 at 5:37 PM, agks mehx <[email protected]> wrote:
> I remember that one had to specify mailet packages in
> conf/mailetcontainer.xml when I first downloaded M2. But now, in M3
> snapshot I do not see those entries.
>
> Has something changed? There probably is some place where packages are
> being specified because the standard mailet classes are being configured
> without the full package path in their names (in mailetcontainer.xml)
>
> Please advise - thanks!
>
