Yes, that's it.
But what is the advantage of creating a new service in Roger's solution ?
Isn't the default service usable in this case like the solution
described in the blog
http://www.behindthesite.com/blog/C1931765677/E2094832857/index.html
Mark wrote:
I think what Stephane originally wanted to do is use Tapestry to
generate the content.
Once he has the content, it goes out via JavaMail API.
I guess Roger's solution should be the way to do that.
MARK
Andreas Bulling wrote:
On 03. Mai 2006 - 23:02:53, Mark wrote:
| I would agree with you if Tapestry would be used for email only and
| nothing else, but if you have an application that is all Tapestry
and in | one or two places the application requires sending out an
email, I think | using Tapestry for that would make more sense than
to add (meaning | deploy, configure and learn) a whole different
framework just for one or | two short emails...
Well, for "one or two short emails" I would use the JavaMail API which
is not that difficult...
Andreas
---------------------------------------------------------------------
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]
--
Stéphane Decleire
05 56 57 99 20
06 63 78 69 06
