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
--
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu_at_jabber.ccc.de * icq: 48874445 * fon: ++49 176 2447 2771
"One dreaming alone, it will be only a dream; many dreaming together
is the beginning of a new reality." (Hundertwasser)