I would recommend not touching the Spring beans from inside a Mailet. Personally, I think of a Mailet as a kind of a Servlet. We don't call spring beans directly from a Servlet. Most of the time we have some kind of "Business Delegate" or "Facade" that's responsible for handling business logic in the back that controls the overall flow of a use case and manages transactions etc.
I may have misunderstood what you mean by making SAC visible from James. Are you wondering where you would instantiate the SAC? The 'init' method of your Mailet would be a good place to load the AppContext. Hope this helps. On Tue, Mar 17, 2009 at 7:57 AM, Corrado Alesso <[email protected]>wrote: > Hello everyone. > > I have to write a Mailet for the James Mail Server, and the Mailet is going > to need some collaborators defined as Spring Beans. > > Do you have any advice about how to architect this system? My problems are > about Spring Application Context visibility from James. > > Thank you, > Corrado > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
