Hi, On Fri, Nov 30, 2012 at 9:23 PM, <[email protected]> wrote: > Basically, we're doing some early research into being an email provider for > our application users. So there are a couple of things I'm trying to figure > out: > > 1. How do I tie together James authentication and our application > authentication so I don't have to manage two user sets?
You should look into james server [1] for that - go over the data-* stuff - it's responsible for user and domain management. We have API + implementations for LDAP, DB, file, etc. James App is a project that binds all James Project email components into the email server. It's Spring based. You can get a sense of how things work together by looking at the beans. > > 2. How do I hook a mailet into our application for things like email > notifications? I was hoping that the mailet could use our existing OSGi > services, but we may be able to get around it some other way -- like sockets > or maybe polling from the application instead of pushing from the mail server. Mailets are designed to do email processing into a mailet container, so the easiest thing would be to expose a service from your app via plain socket/HTTP. > > It would be nice to run in Karaf, but I think a lot of my problems can be > solved just by getting a better understanding for how James works. And I'd > definitely be interested in helping, but I'm not sure how much time I can > give. What do you mostly need help with? > Making things OSGi ready and checking to see if they are ok (package exports/imports and all of that). Any help would be appreciated, even issue reporting/testing. Also see if [2] is of any help. Cheers, [1] http://svn.apache.org/repos/asf/james/server/trunk/ [2] http://berlinbuzzwords.de/sessions/apache-james-more-emails-cloud > -----Original Message----- > From: "Ioan Eugen Stan" <[email protected]> > Sent: Friday, November 30, 2012 1:17pm > To: "James Users List" <[email protected]> > Subject: Re: OSGI app/mailet integration question > > Hello Nate, > > There has been some work done on James towards moving it to OSGi. I'm > working on making James run inside Karaf[1] but it's very early work, > not all components/dependencies are OSGi ready yet. It will take some > time. > > I'm not sure I fully understand what you are trying to achieve. Are > you going for a full James-Karaf integration or run James as a > separate service and integrate over sockets? I think integrating over > sockets would be faster right now (I'm new to OSGi). > > I could use a helping hand in moving James-Karaf forward and I think > it would benefit you too. I know James structure and could use help > with OSGi. Care to help? > > [1] https://github.com/ieugen/james-karaf > > On Fri, Nov 30, 2012 at 7:45 PM, <[email protected]> wrote: >> Hey all, >> >> I'm developing an OSGI-based application where we'd like to tie in mail >> sending/receiving for our app users. Ultimately, I'd like to have a mailet >> that has access to to the OSGI services on our Karaf instance, but I'm not >> sure how to go about it. Also, we're going to need some way to keep users >> and domains synchronized between our app and James. Should I try to extend >> and run James as an OSGI service or is there a simpler way to tie things >> together? >> >> Thanks! >> >> Nate Morrow >> Concept Aware, Inc. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Ioan Eugen Stan / CTO / http://axemblr.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Ioan Eugen Stan / CTO / http://axemblr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
