Hello Luca, the XML-Documents stored in the database will include tags representing dynamic data. In my simple example I used an <xsp-request:get-header name="user-agent"/> XSP-Tag/Logicsheet.
A more practical example. I plan to maintain an list with all links used on the site and an collection of media files (mainly pictures and pdf-files). Editors will use simple tags like <link id="report-2002-01-17-aa"/>. Uploading and editing the reports will be done by other people. A logicsheet could accomplish the jop of retrieving the uri from the database. Makes this sense? Regards Stefan ----- Original Message ----- From: "Luca Morandini" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 11:27 PM Subject: RE: XSP<- XSL<-XML<- for example Xindice > Stefan, > > just one thing, I can't understand why you need the XSP-generation step. You > can get rid of extra tags with XSL... or am I missing something ? > > As I matter of fact I retrieve (and render in HTML) data from Oracle > (including HTML fragments) without using a single XSP line. > > Best regards, > > --------------------------------------------- > Luca Morandini > GIS Consultant > [EMAIL PROTECTED] > http://utenti.tripod.it/lmorandini/index.html > --------------------------------------------- > > > > -----Original Message----- > > From: Stefan [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 17, 2002 11:21 PM > > To: [EMAIL PROTECTED] > > Subject: XSP<- XSL<-XML<- for example Xindice > > > > > > Hello everyone, > > > > I am working on a simple site. The idea is > > > > - storing XML-Data in some Database like Xindice, > > - using Cocoon2 for processing and transformation. > > > > For static data everything works fine. I am not sure, how to design the > > system for prosessing dynamic content. I did an very small example, that > > works in theory but has very poor performance. I guess I just did > > not catch > > the point yet. Any hints would be appreciated. > > > > 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? > > > > Keeping things simple, I simulate the the Xindice-part with just > > a plain XML > > File. This part of the sitemap looks like this: > > > > > > <map:match pattern="generate-xsp"> > > <map:generate type="file" src="xsp-test/generate-xsp.xml"/> > > <map:transform src="xsp-test/generate-xsp.xsl"/> > > <map:serialize type="xml"/> > > </map:match> > > > > Fine. Next I use the pseudo protocol "cocoon" with the xsp generator to > > proceed and process the xsp and transform, serialize it to html. > > > > <map:match pattern="xsp"> > > <map:generate type="serverpages" src="cocoon:/generate-xsp"/> > > <map:transform src="xsp-test/generate-html.xsl"/> > > <map:serialize type="html"/> > > </map:match> > > > > 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? > > > > 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? > > > > Regards > > Stefan > > > > -- > > Stefan > > > > > > --------------------------------------------------------------------- > > 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]> > > > > > > > --------------------------------------------------------------------- > 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]> > --------------------------------------------------------------------- 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]>