Re[4]: Chaining XML->XSP->XML->XSP->etc.

[Sandor Spruit <sa...@cs.uu.nl>]

Luca,

On Friday, February 23, 2001, 3:17:22 PM, you wrote:

Luca> Sandor,

Luca> ahem... this was not *exactly* the problem I face; to make
Luca> things clear, let's suppose you have more than one XSP page to
Luca> go through, like:

I see your point.

[example snipped]

Luca>         How you do this ?

You can't. It's said somewhere, either on this list or in the docs,
that you cannot call on the XSP processor more then once per request.

Luca> The idea, basically, is to have a more complex pipeline than
Luca> just the usual XML -->> XSP --> XSL --> HTML. I'd like to have a
Luca> pipeline with more XSP pages / taglibs in between.

Personally, I'm not too fond of the XSP mechanism :) I can see it's
merits alright, but there are also weaknesses - like the one that
shows up in your example.

Luca> Sure, you can always build a giant taglib custom-made for your
Luca> application; a taglib which does everything inside it... but
Luca> then, how to re-use all those specialized taglibs you can find
Luca> (or develop yourself) when the next application comes ?

Good point. Nice issue to chew on :)

Regards,
Sandor

-- 
ir A.G.L. Spruit, Utrecht University, the Netherlands
Institute of information and computing sciences
"There is a bit of magic in everything, and then some
loss to even things out" (from: Lou Reed, "Magic and Loss")

RE: Re[4]: Chaining XML->XSP->XML->XSP->etc.

[Luca Morandini <l....@tin.it>]

> You can't. It's said somewhere, either on this list or in the docs,
> that you cannot call on the XSP processor more then once per request.
>

	Yes, but I was toying with the idea of serial requests...

	I tried even to trigger them from the browser (writing, at the same time,
one XML and a small HTML whose only purpose is to display a "Wait" message
and call the XML page just written), it worked but...

	how to let processing instructions be ignored from the first XML and be
processed by the second ?

	Moreover...	how to let custom-made tags be ignored from the first XML and
be processed by the second ?

	I think I should wait for Cocoon 2 to be completed...

Best regards,


P.S.
	by the way, I forgot to thank you for your help !
It always moves me when people help complete strangers :)

 
---------------------------------------------
               Luca Morandini
               GIS Consultant
            lmorandini@ieee.org
          +39 (0)744  59 85  1 Office
          +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------


> -----Original Message-----
> From: Sandor Spruit [mailto:sandor@cs.uu.nl]
> Sent: lunedì 26 febbraio 2001 10.28
> To: Luca Morandini
> Subject: Re[4]: Chaining XML->XSP->XML->XSP->etc.
>
>
>
> Luca,
>
> On Friday, February 23, 2001, 3:17:22 PM, you wrote:
>
> Luca> Sandor,
>
> Luca> ahem... this was not *exactly* the problem I face; to make
> Luca> things clear, let's suppose you have more than one XSP page to
> Luca> go through, like:
>
> I see your point.
>
> [example snipped]
>
> Luca>         How you do this ?
>
> Luca> The idea, basically, is to have a more complex pipeline than
> Luca> just the usual XML -->> XSP --> XSL --> HTML. I'd like to have a
> Luca> pipeline with more XSP pages / taglibs in between.
>
> Personally, I'm not too fond of the XSP mechanism :) I can see it's
> merits alright, but there are also weaknesses - like the one that
> shows up in your example.
>
> Luca> Sure, you can always build a giant taglib custom-made for your
> Luca> application; a taglib which does everything inside it... but
> Luca> then, how to re-use all those specialized taglibs you can find
> Luca> (or develop yourself) when the next application comes ?
>
> Good point. Nice issue to chew on :)
>
> Regards,
> Sandor
>
> --
> ir A.G.L. Spruit, Utrecht University, the Netherlands
> Institute of information and computing sciences
> "There is a bit of magic in everything, and then some
> loss to even things out" (from: Lou Reed, "Magic and Loss")
>
>
>
> ---------------------------------------------------------------------
> 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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>