> > A reference to this object is maintained throughout a single use of the
> > pipeline
> > component. By updating this reference Cocoon can store caching
information
> > determined after pipeline setup; since Cinclude instructions are
embedded in
> > the
> > source document, this must be how t
On Mon, 2003-10-20 at 19:21, Horsfield, Peter A. wrote:
> Hello everyone!
>
> I'd just like to thank you all for your input on this thread.
>
> Lars interpreted my email correctly as a request not to exclude the
> document()
> function - not that it is a panacea.
>
> Robert - thanks for champi
Hi,
> -Original Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 20, 2003 1:29 PM
> To: [EMAIL PROTECTED]
>
> Lars Huttar wrote:
> > I am using regular xalan. I haven't tried the others, though
> > I've considered switching to Saxon since there are some oth
Lars Huttar wrote:
I am using regular xalan. I haven't tried the others, though
I've considered switching to Saxon since there are some other
cases where it seems to do better (specifically, in reporting
errors).
Unfortunately, Saxon tended to produce NPEs with document()
in C2.0.4 and an earlier 2
Hello Rob,
Thanks for your helpful suggestions.
Actually, I feel dumb, but ... I can't reproduce the bug anymore.
:-S
So I guess for the time being I'll leave things as they are,
since whatever changes I might make, I wouldn't be able to tell
whether they were helping.
> Are you using XSLTC? Hav
Peter
P.S. My apologies if I missed anyone.
--
Peter Horsfield
http://xml.grumpykitty.biz/
-Original Message-
From: Robert Koberg [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 10:42 AM
To: [EMAIL PROTECTED]
Subject: RE: Crusading for the XSLT docum
Hi Lars,
Are you using XSLTC? Have you tried the regular xalan or saxon? I remember
reading recently on xalan-dev about a bug in relative path resolution in
xsltc.
Also xsltc and regular xalan use two different ways of assigning the
URIResolver. Perhaps cocoon is geared toward one or the other. S
> From: Bruno Dumon
...
> However, in your case you don't need caching, which you can
> easily work
> around with by putting the pipeline inside a with an
> attribute type="noncaching".
Thanks, I will try that.
> > OK.
> > I guess I should submit a bug report to bugzilla. (That's
> all I can
On Mon, 2003-10-20 at 15:49, Lars Huttar wrote:
> E.g. the response to my report of an apparent bug
> in Cocoon's handling of a document() URI, in the
> "problem with relative URI in document() in XSLT in Cocoon" thread:
>
> > You shouldn't use document() in Cocoon style sheets anyway, for a
> >
]
Sent: Monday, October 20, 2003 9:49 AM
To: [EMAIL PROTECTED]
Subject: RE: Crusading for the XSLT document() function
Steven Noels wrote:
> Lars Huttar wrote:
>
> > I think Peter's email that started this thread was not saying
> > that only document() should be used, but
Steven Noels wrote:
> Lars Huttar wrote:
>
> > I think Peter's email that started this thread was not saying
> > that only document() should be used, but rather asking,
> > why exclude document()?
>
> There's a big difference between 'excluding', and 'not
> recommending for
> specific usecases'
-Original Message-
From: Robert Koberg [mailto:[EMAIL PROTECTED]
Sent: Friday, October 17, 2003 6:31 PM
To: [EMAIL PROTECTED]
Subject: RE: Crusading for the XSLT document() function
It is amazing that no one has commented on this post. Perhaps it is because
the beta-omega developers do
Lars Huttar wrote:
I think Peter's email that started this thread was not saying
that only document() should be used, but rather asking,
why exclude document()?
There's a big difference between 'excluding', and 'not recommending for
specific usecases'. AFAIK, nobody 'excluded' the use of document
> 1) it hides away the aggregation instruction into an XSLT stylesheet,
> which might (or might not) be obvious to debug for somebody who isn't
> the original author.
I would prefer to keep details hidden away from the main
program outline, if they only affect one or a few components.
When somet
Hi Steven,
> -Original Message-
> From: Steven Noels [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 18, 2003 12:09 PM
> To: [EMAIL PROTECTED]
>
> In my very personal opinion, I'm not convinced one should use document()
> for aggregation purposes, since:
>
> 1) it hides away the aggr
Robert Koberg wrote:
It is amazing that no one has commented on this post. Perhaps it is because
the beta-omega developers do not want to show anything that contradicts the
alpha developer (fear of agora Siberia perhaps...).
Don't you worry about Siberia - everybody is free to think whatever he
w
It is amazing that no one has commented on this post. Perhaps it is because
the beta-omega developers do not want to show anything that contradicts the
alpha developer (fear of agora Siberia perhaps...).
You show a way to use cocoon and the document function in a harmonious (and
a very useful) way
document('cocoon:/myinternalpipeline');
SoC... Caching... Virtual URI space... Pipeline reuse...
All it would take is for Cocoon to keep an eye out for calls to the
SourceResolver, and perhaps for request parameters to be
passed smartly. Better yet, force all document('...') requests b
18 matches
Mail list logo