Return-Path: 
 <cocoon-dev-return-13026-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 61802 invoked by uid 500); 5 May 2001 20:22:58 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 61786 invoked from network); 5 May 2001 20:22:57 -0000
Date: Sat, 5 May 2001 16:22:50 -0400 (EDT)
From: Donald Ball <balld@webslingerZ.com>
X-Sender: <balld@localhost.localdomain>
To: <cocoon-dev@xml.apache.org>
Subject: Re: XincludeSAXconnector
In-Reply-To: <Pine.LNX.4.31.0105051952460.1154-100000@lap1.otego.com>
Message-ID: <Pine.LNX.4.30.0105051621140.2986-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

On Sat, 5 May 2001, giacomo wrote:

> > > Can anyone mail/post an exmaple for the XIncludeSAXconnector?
> > > I don't really understand how this thing works.
>
> I'm working on a sample which shows how to use it but IIRC the element
> is like:
>
>   <anyroot xmlns:xinclude="http://www.w3.org/1999/XML/xinclude">
>     <xinclude:include src="foobar"/>
>   </anyroot>
>
> where the foobar from the src attribute denotes a url from the sitemap.
> For the other attributes please look at
> src/org/apache/cocoon/components/saxconnector/XIncludeSAXConnector.java.
>
> > and would the authors of this component care to address my concerns about
> > its namespace - that is to say, should we change the namespace on which it
> > operates or patch it to conform to the xinclude spec?
>
> Ok, let's change the namespace uri. Do you have a suggestion?

hmm, something like http://apache.org/cocoon/include/1.0 would work :)

> > (i still don't think
> > we need to be able to do xincludes via this hidden mechanism when we can
> > do it explicitly using the transformer, but it's not a strong opinion).
>
> This is not correct. The XIncludeTransformer is not capable of using
> sitemap URLs (and I honestly don't see it to be available to "normal"
> sitemap component). Whereas XIncludeSAXConnector is *only* able to get
> its included events directly from a sub pipeline from sitemap URLs and
> this is a big advantage over XIncludeTransformer (not to mention the
> view point of the cache).

ah, okay, that makes perfect sense. still not sold on the architecture,
but that's neither here nor there.

- donald


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