I quote the important part of this commit. I added to the assembly the 2 new blocks (I also added the 2 interfaces to the services packages). The <matcherpackages> and <mailetpackages> configurations are now toplevel confs and not subconf of the <spoolmanager>.
This allowed me to remove some avalon container specifics from the spoolmanager (no more service passing from spoolmanager to its subcomponents) and this combined with following patches will allow us to have multiple components behaving in the same server (multiple spools, multiple smtpserver.. ) You can also easily replace the mailet/matcher loading mechanism without to change the james core. Stefano > Modified: james/server/trunk/src/conf/james-assembly.xml > URL: > http://svn.apache.org/viewcvs/james/server/trunk/src/conf/jame > s-assembly.xml?rev=233561&r1=233560&r2=233561&view=diff > ============================================================== > ================ > --- james/server/trunk/src/conf/james-assembly.xml (original) > +++ james/server/trunk/src/conf/james-assembly.xml Fri Aug 19 > 14:20:16 > +++ 2005 > @@ -37,8 +37,17 @@ > > <!-- The James Spool Manager block --> > <block name="spoolmanager" > class="org.apache.james.transport.JamesSpoolManager" > > - <provide name="James" role="org.apache.mailet.MailetContext"/> > <provide name="mailstore" > role="org.apache.james.services.MailStore"/> > + <provide name="matcherpackages" > role="org.apache.james.services.MatcherLoader"/> > + <provide name="mailetpackages" > + role="org.apache.james.services.MailetLoader"/> > + </block> > + > + <block name="matcherpackages" > class="org.apache.james.transport.JamesMatcherLoader" > > + <provide name="James" role="org.apache.mailet.MailetContext"/> > + </block> > + > + <block name="mailetpackages" > class="org.apache.james.transport.JamesMailetLoader" > > + <provide name="James" role="org.apache.mailet.MailetContext"/> > </block> > > <block name="dnsserver" > class="org.apache.james.dnsserver.DNSServer" /> > > Modified: james/server/trunk/src/conf/james-config.xml > URL: > http://svn.apache.org/viewcvs/james/server/trunk/src/conf/jame > s-config.xml?rev=233561&r1=233560&r2=233561&view=diff > ============================================================== > ================ > --- james/server/trunk/src/conf/james-config.xml (original) > +++ james/server/trunk/src/conf/james-config.xml Fri Aug 19 14:20:16 > +++ 2005 > @@ -18,7 +18,7 @@ > <!-- In case the defaults do not suit you, the items you are > most likely to need to change --> > <!-- are preceded by a CHECKME! or CONFIRM? comment in the > left margin. --> > > -<!-- For production use you will probably need to make more > extensive changes, see --> > +<!-- For production use you will probably > +n"src/conf/james-assembly.xml"eed to make more extensive > changes, see > +--> > <!-- http://james.apache.org/documentation_2_1.html --> > > <!-- $Revision$ Committed on $Date$ by: $Author$ --> @@ > -98,15 +98,25 @@ > --> > </James> > > - <!-- This is an example configuration for FetchMail, a > JavaMail based gateway --> > - <!-- service that pulls messages from other sources, and > inserts them into the --> > - <!-- spool. They are then processed normally, although > FetchMail generally --> > - <!-- has to fabricate some of the envelope information. > FetchMail should be --> > - <!-- considered a mail gateway, rather than a relay, in > RFC terms. --> > - <!-- Fetchmail is a functionally richer replacement for > FetchPOP. --> > - <!-- CHECKME: FetchMail is disabled by default, and must > be configured to use. --> > - <!-- Edit the file referred to by fetchmailConfig to > enable and configure. --> > - &fetchmailConfig; > + <!-- This is an example configuration for FetchMail, a > JavaMail based gateway --> > + <!-- service that pulls messages from other sources, and > inserts them into the --> > + <!-- spool. They are then processed normally, although > FetchMail generally --> > + <!-- has to fabricate some of the envelope information. > FetchMail should be --> > + <!-- considered a mail gateway, rather than a relay, in > RFC terms. --> > + <!-- Fetchmail is a functionally richer replacement for > FetchPOP. --> > + <!-- CHECKME: FetchMail is disabled by default, and must > be configured to use. --> > + <!-- Edit the file referred to by fetchmailConfig to > enable and configure. --> > + &fetchmailConfig; > + > + <!-- Set the Java packages from which to load mailets and > matchers --> > + <mailetpackages> > + > <mailetpackage>org.apache.james.transport.mailets</mailetpackage> > + > <mailetpackage>org.apache.james.transport.mailets.smime</maile > tpackage> > + </mailetpackages> > + <matcherpackages> > + > <matcherpackage>org.apache.james.transport.matchers</matcherpackage> > + > <matcherpackage>org.apache.james.transport.matchers.smime</mat > cherpackage> > + </matcherpackages> > > <!-- The James Spool Manager block --> > <!-- --> > @@ -114,16 +124,6 @@ > <spoolmanager> > <!-- Number of spool threads --> > <threads> 10 </threads> > - > - <!-- Set the Java packages from which to load mailets > and matchers --> > - <mailetpackages> > - > <mailetpackage>org.apache.james.transport.mailets</mailetpackage> > - > <mailetpackage>org.apache.james.transport.mailets.smime</maile > tpackage> > - </mailetpackages> > - <matcherpackages> > - > <matcherpackage>org.apache.james.transport.matchers</matcherpackage> > - > <matcherpackage>org.apache.james.transport.matchers.smime</mat > cherpackage> > - </matcherpackages> > > <!-- The root processor is a required processor - > James routes all mail on the spool --> > <!-- through this processor first. --> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
