I have a struts application that makes use of an email service layer.
The email service provides a merge facility (via Velocity) and a
delivery facility (via JavaMail).
Typically, the application invokes the mail service within a struts
action, where it has access to the request to get the rel
Since this is an ActionMapping subclass, then 'className' is the
attribute used to declare it in the struts config, not 'type'; 'type'
refers to the Action class to use.
As written there, of course, 'type' could be taken less literally to
mean the class of the ActionMapping.
Unfortunately, the
Nathan,
I briefly looked into using jsp for email templating recently, and
decided that it was not the right fit for the task in my situation.
Instead I ended up building a basic template merge facility using
Velocity, and a mail sender facility based on JavaMail. I tied them
together with a t
A bit late to the party, but...
Firstly, I'd second what Joe said about PlugIns vs
ServletContextListener: in more than one instance I've found that using
ServletContextListener that does service/model initialization paid off
when I later wanted to use the same service layer in a non-Struts web
My experience with this has been a blend of some of what's been said so
far, with a bit of sugar on top.
I agree with those who say that the filesystem and a stock webserver
(apache) are the way to server images - and all static content, imho.
(ymmv) Particularly since your image data is dyna
5 matches
Mail list logo