cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: Context:// issue
Date Tue, 29 May 2001 05:13:34 GMT
On Tue, 29 May 2001, Donald Ball wrote:

> On Sun, 27 May 2001, Berin Loritsch wrote:
>
> > The context and resource protocols should match the semantics for
> > file and jar:
> >
> > context://relative/path/from/context/root
> > resource://path/to/packaged/resource
>
> why don't we go ahead and enumerate all of the extra protocols recognized
> by c2 and their semantics, and stick them in a document for reference.
> i'll take a stab:
>
> context urls point to xml resource pipelines relative to the root of the
> current sitemap. the same context url in two seperate sitemaps can resolve
> to two seperate pipelines. format: context://{path}

The context protocol point into the file system and not to resource
pipeline. But yes, the same context url in two seperate sitemaps can
resolve to two seperate files. format: context://{path}

> cocoon urls point to xml resource pipelines relative to the root of the
> current webapp. the same cocoon url in two seperate sitemaps always
> resolves to the same resource pipeline. format: cocoon://{path}.

Not sure here. As your first isn't how you thought which one is relative
to the current sitemap and wich one is not. As this protocol is not
implemented yet we can model it in the way we like it.

> resouce urls point to binary resources that are accessible via the jvm
> classloader. typically, these are data files included in a jar file.
> format: resource://{path}.

Yup

Giacomo


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


Mime
View raw message