Hi Philip,
>Is there much of an advantage to putting
>this functionality in a service?
Sounds like you are in explore mode. Not sure you would benefit from trying
to create a reusable component until you've done at least once the hard way.
>SSL - what were the difficulties?
Mainly the lack of visiblity at the JavaMail API level. There is a good intro
to this at:
http://www.javaworld.com/javatips/jw-javatip115.html
Incidentally I found in bizarre that the only way to get a certificate
generated by OpenSSL into Turbine was to load and reexport the cert
via Internet Explorer. If you have a go at this I would love to hear
your experiences - sorry off topic and moderator starting to cough.
>Also, is TurbineMailService something that already exists?
If it does it is not making much an impact then. :^)
Regards,
Malcolm
-----Original Message-----
From: Philip S. Wachtel [mailto:[EMAIL PROTECTED]
Sent: 09 July 2003 14:49
To: Turbine Users List
Subject: Re: Turbine Architecture Question
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hi Malcolm,
Yes, the object is to create a web interface to mail without developing an
entire Javamail facade. The reason I didn't want to do that is because it
seemed like more work than it was worth as I would just wind up re-created
most of the methods that I need. Is there much of an advantage to putting
this functionality in a service?
I wasn't thinking about SSL, but, now that you mention it, what were the
difficulties? It's not out of the question that I'll need SSL in the
future.
Also, is TurbineMailService something that already exists? I couldn't find
it (I did a quick google search and came up with nothing).
I appreciate your help.
Regards,
Philip
----- Original Message -----
From: "Malcolm Kendall" <[EMAIL PROTECTED]>
To: "Turbine Users List" <[EMAIL PROTECTED]>; "Philip S.
Wachtel" <[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 7:19 AM
Subject: RE: Turbine Architecture Question
> N�T�,j�j�kj{ z��w�.�k?�oz�"�z
> ?��x?j~��Hi Philip,
> This was the same problem that we encountered. I didn't know about
TurbineMailService so went
> the Screen (java) -> Javamail route. For velocity stuff a facade object on
a Message seems to work,
> it makes the templating alot easier to do, but maybe this is what you
wanted to avoid doing (
> custom objects). Will you be using SSL for secure access to mail servers?
That seemed a little
> tricky to get working.
> Regards,
> Malcolm Kendall
>
> -----Original Message-----
> From: Philip S. Wachtel [mailto:[EMAIL PROTECTED]
> Sent: 08 July 2003 19:02
> To: Turbine Users List
> Subject: Turbine Architecture Question
>
>
> Hi there,
>
> I'm trying to find an answer to a design question.
>
> I would like to build a web interface to an IMAP/SMTP server. Think
hotmail. At first, I thought it would make sense to create a mail service
the screens could use to access the IMAP and SMTP server. Now, however, I'm
losing confidence in that idea because I can't find a way to really hide the
workings of Javamail, which is what I'm using.
>
> My layers, as I saw it, were:
>
> Screen (vm) --> Screen (java) -- > TurbineMailService -->
Javamail -(IMAP/SMTP proto)-> Mail Server
>
> But, the problem is that the TurbineMailService would wind up having to
convert Javamail objects to custom objects for the screens. This just
doesn't make sense to me.
>
> So, the bottom line questions is, what would be a better approach to this?
I could just use the Javamail tools directly in the screens? Seems messy,
but more straight forward.
>
> Thanks for your suggestions.
>
> Regards,
> Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
