RE: XSP<- XSL<-XML<- for example Xindice

[Luca Morandini]

Stefan,

hey, real programmers start doing the real work after midnight !

Anyway, it is past midnight in Italy as well... time to rest after this last
stored procedure.

Good night !

-
   Luca Morandini
   GIS Consultant
  [EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Stefan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 18, 2002 12:14 AM
> To: [EMAIL PROTECTED]
> Subject: Re: XSP<- XSL<-XML<- for example Xindice
>
>
> Thank You Vadim and Luca,
>
> I will think about Your proposals tomorrow. For sure they will guide me in
> the right direction. Midnight passed in Germany,
>
> Thanks again
> Stefan
>
> - Original Message -
> From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, January 17, 2002 11:46 PM
> Subject: RE: XSP<- XSL<-XML<- for example Xindice
>
>
> > > From: Stefan [mailto:[EMAIL PROTECTED]]
> >
> > 
> >
> > 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  etc. elements. So at least I have to
> > > enclose the things in an  element. Right?
> >
> > Why do you want to create XSP out of dynamic data? What's the reason?
> >
> > 
> >
> > > 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]>
> >
>
>
> -
> 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]>

Re: XSP<- XSL<-XML<- for example Xindice

[Stefan]

Thank You Vadim and Luca,

I will think about Your proposals tomorrow. For sure they will guide me in
the right direction. Midnight passed in Germany,

Thanks again
Stefan

- Original Message -
From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 17, 2002 11:46 PM
Subject: RE: XSP<- XSL<-XML<- for example Xindice


> > From: Stefan [mailto:[EMAIL PROTECTED]]
>
> 
>
> 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  etc. elements. So at least I have to
> > enclose the things in an  element. Right?
>
> Why do you want to create XSP out of dynamic data? What's the reason?
>
> 
>
> > 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]>
>


-
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]>

RE: XSP<- XSL<-XML<- for example Xindice

[Luca Morandini]

 Stefan,

 the same task may be carried out by stylesheets using
 SQLTransformer... possibly using stored procedures, in order to
 take the task of dealing with persistent data out of Cocoon (a
 much cleaner design too :) ).

 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:51 PM
> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: XSP<- XSL<-XML<- for example Xindice
> >
> >
> > Hello Luca,
> >
> > the XML-Documents stored in the database will include tags representing
> > dynamic data. In my simple example I used an  > 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 .
> > 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  etc. elements. So at
> least I have to
> > > > enclose the things in an  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:
> > > >
> > > >
> > > > 
> > > >   
> > > >   
> > > >   
> > > > 
> > > >
> > > > Fine. Next I use the pseudo protocol "cocoon" with the xsp
> > generator to
> > > > proceed and process the xsp and transform, serialize it to html.
> > > >
> > > > 
> > > >   
> > > >   
> > > >   
> > > > 
> > > >
> > > > 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.
> > > >
> >

Re: XSP<- XSL<-XML<- for example Xindice

[Stefan]

Hello Luca,

the XML-Documents stored in the database will include tags representing
dynamic data. In my simple example I used an  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 .
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  etc. elements. So at least I have to
> > enclose the things in an  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:
> >
> >
> > 
> >   
> >   
> >   
> > 
> >
> > Fine. Next I use the pseudo protocol "cocoon" with the xsp generator to
> > proceed and process the xsp and transform, serialize it to html.
> >
> > 
> >   
> >   
> >   
> > 
> >
> > 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]>

RE: XSP<- XSL<-XML<- for example Xindice

[Vadim Gritsenko]

> From: Stefan [mailto:[EMAIL PROTECTED]]



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  etc. elements. So at least I have to
> enclose the things in an  element. Right?

Why do you want to create XSP out of dynamic data? What's the reason?



> 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. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

RE: XSP<- XSL<-XML<- for example Xindice

[Luca Morandini]

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  etc. elements. So at least I have to
> enclose the things in an  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:
>
>
> 
>   
>   
>   
> 
>
> Fine. Next I use the pseudo protocol "cocoon" with the xsp generator to
> proceed and process the xsp and transform, serialize it to html.
>
> 
>   
>   
>   
> 
>
> 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]>

XSP<- XSL<-XML<- for example Xindice

[Stefan]

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  etc. elements. So at least I have to
enclose the things in an  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:



  
  
  


Fine. Next I use the pseudo protocol "cocoon" with the xsp generator to
proceed and process the xsp and transform, serialize it to html.


  
  
  


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. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>