> I have been following this thread with some interest because, although I
> plan (eventually) to add the ability to generate PDFs to my XML-based
> content management system. Right now, I mostly generate HTML, but I've
been
> constructing this system to not be specific to any one rendering
mechanism.
>
> Basically, I had planned to use XSL-FO to generate intermediate files and
> distill them using Acrobat automatically. However, I don't want to do that
> "on-demand", but rather when necessary, and simply store the resulting PDF
> on a web server, file server, FTP server, etc depending on where I was
> sending data. Users could then access these stored PDFs and I could update
> them as necessary.
>
> Does this seem like a reasonable solution? I have no need (currently or
> anticipated) to generate PDF "on-demand", but from my reading of this
> thread, I could do that with FOP if I have a burning need for it.
>
> Regards and thanks,
>
> Corey Snow

Hello Corey,

we tried successfully another method: We use CVS for version management.
There you can setup a watcher on documents. As soon as a new version of some
XSL Fo file is committed, the FOP process is started. And if somebody
requests this PDF, he always gets the latest version.

Joerg


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list