Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-Id: <200310201443.h9KEhxb02476@server1.livestoryboard.com>
From: "Robert Koberg" <rob@koberg.com>
To: <users@cocoon.apache.org>
Subject: RE: Crusading for the XSLT document() function
Date: Mon, 20 Oct 2003 07:41:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <001801c39716$7bd90240$66051e43@dallas.sil.org>
Thread-Index: AcOXFpa0LQYyocW6S+q4r79UCmC5ogAAPFmw

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. Saxon has =
the
best solution (it uses both ways) so it might be the best choice. I have
posted some info on both commons-dev and xalan dev about the issue that
should be in the archives but if you want further info, let me know.

Best,
-Rob

> -----Original Message-----
> From: Lars Huttar [mailto:lars_huttar@sil.org]
> Sent: Monday, October 20, 2003 7:29 AM
> To: users@cocoon.apache.org
>=20
> > 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 <map:pipeline> with an
> > attribute type=3D"noncaching".
>=20
> Thanks, I will try that.
>=20
> > > OK.
> > > I guess I should submit a bug report to bugzilla. (That's
> > all I can do.)
> >
> > there is/was already one, but it was then closed an moved as a =
feature
> > request to a wiki page:
> > http://wiki.cocoondev.org/Wiki.jsp?page=3DCocoonFeatureRequests
>=20
> I saw this one, which says
>=20
> #  Modify the caching system so that it is possible to:
>=20
>     * include docs referenced by XSLT's document() in the cache =
validity
> (bugzilla 10203)
>=20
> But I don't think that covers the problem I'm referring to...
> please correct me if I'm wrong.
> This "feature request" sounds like it's asking for Cocoon to keep
> track of whether the document accessed by document() from a stylesheet
> has been modified; the only problem this feature is intended to solve,
> if I understand it, is that a certain request might return old data
> when the referenced document has been changed.
>=20
> The problem I'm referring to is one where document() doesn't find
> the requested document in the first place, due to faulty =
URI-resolution.
>=20
> Anyway I submitted bug report 23939 before I saw your latest email.
> I hope it can be distinguished from the above feature request.
>=20
> Lars
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org