Hi, first of for your requirements current development version of james would be a better fit then the last released stable one. Current development version of james use spring for dependecy injection. There is currently no war file but writing a war deployment shouldn't be to hard (its on my todo list).
I use james as standalone application (development version). When using development version of james you could just inject the UsersRepository into your class instance via JSR250 and use it for all kind of user actions. The other solution would be to use jmx. Hope this helps. Bye, Norman Ps: Feel free to poke me again 2010/2/11 N Kapshoo <nkaps...@gmail.com>: > I want to evaluate James as an integrated mail solution for a very large web > application. > > I have successfully deployed on my local box and used JavaMail to test basic > email. > > What I am unclear about is - > How are production deployments of James typically done? I would be looking > to support a very large volume of email and would also be writing a webmail > solution that sits with the rest of our application. > Is James typically deployed inside a servlet container for production? How > do I go about writing mailets and deploying them? > > Lastly, if I want to create/delete users programmatically, how would my java > code in the container make james server api calls? > > Thanks in advance. > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
