Jorg Heymans wrote:
You could make a custom transformer that reads the stylesheet from the
This is not necessary. One could use the cocoon: protocol when specifying the source for the stylesheet. Next, a pipeline for the stylesheet is needed that consists only of the database reader et voil�.
And if you don't like the extra pipeline, consider creating a source for relational databases.
Also, you'll want to look into caching this result for performance reasons. Caching database driven results can be a tricky thing, of course. Look into the "eventcache" block if you're using 2.1 for one option. The other is to roll your own system - see caching xsp example if you're using xsp. As things stand, I don't think there's an easy caching solution for readers, so you may need to use a simple generate->serialize pipeline for your stylesheet.
Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
