> Ok, I find it. > If I'm right, in order to convert a mailet from 2.2 to 3.0 > > At least, we have to change : > > /* ok with James 2.2.0 > ComponentManager componentManager = (ComponentManager) > getMailetContext().getAttribute( > Constants.AVALON_COMPONENT_MANAGER); > DataSourceSelector datasources (DataSourceSelector) > componentManager.lookup(DataSourceSelector.ROLE); > */ > > ServiceManager serviceManager = (ServiceManager) > getMailetContext().getAttribute( > Constants.AVALON_COMPONENT_MANAGER); > > DataSourceSelector datasources = (DataSourceSelector) > serviceManager.lookup(DataSourceSelector.ROLE);
This is the main difference between james-2.2.1-dev and james-3.0-dev. We have a new version because the component to service change is not backward compatible: the change is needed because component are deprecated in the avalon framework. 3.0-dev will probably change a lot before a 3.0 release and you probably need to change again your mailet to upgrade to future 3.0-dev trunk builds. Probably mailet APIs will change a lot before a 3.0 final. You probably should stick to the current version or to the branch 2_1_fcs (with components and old mailets). > Does someone already list the Mailet API change? > I noticed that all the mailet into the v3 have been changed... The mailet have beed changed mainly to to reflect the componet=>service issue of the avalon framework. I hope that my work on the SMTPServer extensions (PIPELINE fix, AUTH fix, DSN support), the DSNReport attribute to transport delivery-status informations and a reworked RemoteDelivery for better error catching will be committed in the alpha stage of the 3.0 version. I hope that someone will port every james component to POJO objects + avalon adapter/container so it will be faster to support different container (spring, pico or directly a j2ee container). Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
