Hi Kristian,
For this kind of purpose, we use the great Webtest library
(
http://webtest.canoo.com) as a mail processor.
We don't use webtest as is, but trigger it from groovy scripts (think it
could be done with simple java classes
with a proper Ant builder). I think it can be "cronified" by using
Quartz or Glassfish timer
That's what I can say. It fits well to our needs, because we use other
features like web browsing. But there may be
a more simple way to do that.
I'm curious to see what will be proposed to you...
Hope that helps a bit
Cheers
Florent
Pingwy
27, rue des arènes
49100 Angers
Kristian Rink a écrit :
> Folks;
>
> in the process of moving some of our internal apps to JEE/glassfish, I
> have kinda hit a wall right now: Right now we do have a scripted-up
> (Perl and Unix-shell) to do automated processing of incoming (SMTP)
> e-mails, which works more or less bad and is just more or less
> manageable. I want to rebuild this solution in JEE, so I mainly have to
>
> - handle inbound (SMTP) messages
> - extract information using their headers
> - extract body text (if present)
> - dump attachments (if any) to some file
> - import all the mess to our backend DMS.
>
> By now, I considered several options (including implementing a
> message-driven bean and "somehow" let it deal with the
> javax.mail.Message object in question), but somehow all of them seem
> more or less flawed.
>
> So, question: How do you folks handle situations like this from an
> architectural point of view?
>
> TIA for any recommendations, best regards.
> Kristian
>
>