In this case it has to do with the fact that we're using Tiles to ensure that we get a consistent look for all our emails. Basically I've created a Tiles Layout that constructs the emails using tiles to include the text/plain and text/html versions of the content and using action properties to control to, from, cc, bcc, subject and the attachments. I guess I'm confused as to why it's a sin to ask the system for information it obviously has to have? (*Chris*)
On Wed, Jan 7, 2009 at 9:58 AM, Musachy Barroso <musa...@gmail.com> wrote: > If the MIME Emails are generated by tags, why don't you build the URL > in the jsps? > > musachy > > On Wed, Jan 7, 2009 at 12:45 PM, Chris Pratt <thechrispr...@gmail.com> > wrote: > > Basically, I have some tried and true tag libraries for generating > pretty, > > MIME Emails that work great with Struts. They support all manner of > > attachments and have worked great for years. Occasionally I need to > attach > > something (in this case a PDF) that is generated by another action. So > the > > main action needs to have a property that returns a list of things to be > > attached, which in this case is a URL to the Action that generates the > > dynamic PDF. > > > > I'm sure there's a way to refactor all this into some unrecognizable > form, > > but this is tried and true, supports JSP and Tiles including properly > > formatted, pretty HTML and plain text MIME emails, and really I can't see > > any reason that this should be precluded from working with any system > that > > supports JSP Tag Libraries. > > > > Can you see a better way to get the generated attachment into the email? > > (*Chris*) > > > > On Wed, Jan 7, 2009 at 9:23 AM, Dave Newton <newton.d...@yahoo.com> > wrote: > > > >> Chris Pratt wrote: > >> > >>> Strange? I would have thought this was a fairly commonly needed > feature > >>> > >> > >> I've never needed to generate a URL from an action name within another > >> action across a half-dozen S2 apps--it can't be *that* common... I think > the > >> most hackish thing I've done like that is to use an action name as a > dynamic > >> result parameter for a "redirectAction" result type. > >> > >> IMO actions should "never" generate a URL since they're supposed to be > >> decoupled from the underlying action access mechanism. What's your use > case > >> that this solves? > >> > >> Dave > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > >> For additional commands, e-mail: user-h...@struts.apache.org > >> > >> > > > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
