I saw a thread about attaching a file (possibly url) as an attachment. Will that work for you? I'm going to work on that next week. Maybe we will be able to share some ideas. My requirements are as follows: 1. When user clicks on "Send Email" button. I have an xml String sent to StreamGenerator, then transformed by xsl-fo and serialized by jfor to rtf and displayed on a screen. 2. The next step is to use sendMail to send the created rtf document as an attachment to an email address.
I haven't started to look into it yet. I'm thinking about saving the created rtf in step 1 on the server and then sending it as an attachment. Anyway, more later on this. Charlene -----Original Message----- From: Christian Haul [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2003 7:52 AM To: [EMAIL PROTECTED] Subject: Re: [Error] Sendmail Logicsheet and Cinclude [EMAIL PROTECTED] wrote: > I've been stumbling the past couple of days through the sendmail > logicsheet and sendmail actions in 2.1-M1. > > Here's what I'm trying to do: > > Include generated content (i.e. content produced by a pipeline) into the > body of an email sent by sendmail action or logicsheet. This is possible only by using the util logicsheet. > The sendmail action has been a deadend, so I've looked at the sendmail > logicsheet. Below is mail.xsp, my attempt to implement sending a message Both share the same code, so if one does not work, the other is unlikely to do better. However, mind sharing why the action didn't work out? > body created by a pipeline. Please note that I have defined the > necessary namespaces in the xsp:page element: > <sendmail:body>The results of processing the pipeline triggered at > the uri: workPlanning/contents. are below.<br/> > <!-- NB: the request below has been tested and works when called > directly --> > <cinclude:include src="cocoon://workPlanning/contents" > element="included" /> > </sendmail:body> This does not work as it adds the result of the inclusion to the SAX stream _directed_at_the_client_ while you need to have it as e.g. string to pass to sendmail. The "correct" solution is to use <sendmail:attachment url="cocoon://workPlanning/contents"/> to pull in the generated content. AFAIR you could as well do <xsp:expr><util:get-source uri="cocoon://workPlanning/contents"/></xsp:expr> > I'd appreciate some assistance with this. Once I've found my way around > this problem, I'll write up a how-to for the cocoondev.org wiki. Deal! Chris. -- C h r i s t i a n H a u l [EMAIL PROTECTED] fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- 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]
