> From: Stefan [mailto:[EMAIL PROTECTED]]
<snip/> Stefan, > I set up a pipeline, which gets some XML Data from Xindice und transforms > the data to XSP. This step is required because the retrieved Data always is > enclosed in <resources><resource> etc. elements. So at least I have to > enclose the things in an <xsp:page> element. Right? Why do you want to create XSP out of dynamic data? What's the reason? <snip/> > It is working fine and made me very happy. Thinking twice i realized that > the xsp gets compiled every time. Of course, cocoon cannot know if the xsp > has changed or not. > > I have no idea what to do. I have a strong feeling, that this approach is > very, very bad. But I can't figur out a better solution. > > Could anyone give me some advice? It's totally not clear from you description what do you want to do with the data you obtained from xindice and why you decided to transform this data into XSP. However, I can suggest the following options: 1. Write XSP page which gets data from Xindice using XML:DB API, and process this data inside XSP (example: ESQL); 2. Use XSLT to transform output of xindice into what you want; 3. Write own transformer to do what you want to do; 4. Use aggregation, with any of these methods. > One more question: Isn't this even the case if their is no XSP involved when > using a datastore like Xindice (or a SQL-Database) instead of the local file > system for static xml. I guess cocoon can't cache anything in this case? Cocoon does not cache output of Xindice now; but caching support will be implemented in future, when Xindice provide API to know was content changed or not. Vadim --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
