You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Donald Ball <ba...@webslingerZ.com> on 2000/02/01 19:38:22 UTC
Re: FW: Redirecting users in Cocoon
On Mon, 31 Jan 2000, Stefano Mazzocchi wrote:
> Meanwhile, I'll reply to the XSP questions, but when they deal with
> implementation details, I just don't know more than you do.
>
> Anyway, if you find something you don't like, you know the golden rule:
> fix it yourself! :)
Me, I'm _trying_ to, but no one has voted on my proposal, so I'm just
cooling my heels right now.
- donald
Re: Changing XSP taglib namespace configuration behavior
Posted by Donald Ball <ba...@webslingerZ.com>.
On Sat, 5 Feb 2000, Stefano Mazzocchi wrote:
> > hmm. i'm not 100% sure i understand the desired constraints here. I think
> > what you're saying is that you want me to come up with a solution that
> > lets you map namespace URIs to .xsp files without using the resource://
> > URL? No wait, that doesn't make sense. What exactly do is the problem
> > we're trying to solve?
>
> Avoid the need for special URLHandlers since they limit both portability
> and operation.
So why not have an internal URLResolver class or something like that that
checks the protocol of URLs; if they're in the standard batch supported by
the lowest common denominator of JVMs (that is to say, http, ftp, and
file), just use URLHandler, otherwise use a CocoonURLHandler.
> > Hmm. that's much nicer. The rest of the the configuration file can be
> > rewritten as XML similarly. Anyone have any significant objections and/or
> > suggestions for rewriting cocoon's properties file in XML?
>
> I had this in plan for 2.0 but if you want to do it sooner, I'm ok for
> it.
I altered the cocoon Configurations object to not subclass Properties and
wrote a subclass of Configurations called XMLConfigurations that should
construct a Configurations object from an XML document. Untested so far,
but it compiles. I'll try to test it shortly.
> Ok, what about (having XML-based configs)
>
> <processor name="xsp">
> <library>
> <language name="java"
> <namespace uri="http://www.apache.org/1999/XSP/Request">
> <resource location="classpath"
> path="org/apache/cocoon/processor/xsp/library/java/request.xsl"
> />
> </namespace>
> <namespace uri="http://myownstuff">
> <resource location="file"
> path="/home/mystuff/lib/mystuff.xsl"
> </resource>
> </namespace>
> </language>
> </library>
> </processor>
>
> Hmmm, maybe too verbose... any comment?
Naw, looks pretty good to me. Maybe:
<resource protocol="classpath" path="org.apache.cocoon..."/>
<resource uri="file:///home/myseuff/lib/mystuff.xsl"/>
So you either have (uri) or (protocol,path,???). URIs get passed to
URLFactory, others get passed to CocoonURLHandlers.
Sure, it's verbose, but XML is pretty verbose.
- donald
Re: Changing XSP taglib namespace configuration behavior
Posted by Stefano Mazzocchi <st...@apache.org>.
Donald Ball wrote:
>
> On Wed, 2 Feb 2000, Stefano Mazzocchi wrote:
>
> > Donald Ball wrote:
> > >
> > > On Mon, 31 Jan 2000, Stefano Mazzocchi wrote:
> > >
> > > > Meanwhile, I'll reply to the XSP questions, but when they deal with
> > > > implementation details, I just don't know more than you do.
> > > >
> > > > Anyway, if you find something you don't like, you know the golden rule:
> > > > fix it yourself! :)
> > >
> > > Me, I'm _trying_ to, but no one has voted on my proposal, so I'm just
> > > cooling my heels right now.
> >
> > I vote +1 to your previous proposal.
> >
> > Also, could you please try to come up with a solution that doesn't
> > require us to set a specific URL handler but that doesn't require you to
> > change the configurations out of the box?
>
> hmm. i'm not 100% sure i understand the desired constraints here. I think
> what you're saying is that you want me to come up with a solution that
> lets you map namespace URIs to .xsp files without using the resource://
> URL? No wait, that doesn't make sense. What exactly do is the problem
> we're trying to solve?
Avoid the need for special URLHandlers since they limit both portability
and operation.
> Anyway, what I'm thinking is that we should change the cocoon.properties
> file so that instead of hardcoding prefixes like so:
>
> processor.xsp.library.request.java =
> resource://org/apache/cocoon/processor/xsp/library/java/request.xsl
>
> we hardcode the URIs instead:
>
> processor.xsp.library.java = http://www.apache.org/1999/XSP/Request|resource://org/apache/cocoon/processor/xsp/library/java/request.xsl
>
> more descriptively:
>
> processor.xsp.library.java = namespaceURI|xspURI
>
> hmm. that syntax is atrocious. maybe it's time that we XMLized the
> cocoon.properties file:
>
> <processor name="xsp">
> <library>
> <language name="java"
> <namespace
> uri="http://www.apache.org/1999/XSP/Request"
> lib="resource://org/apache/cocoon/processor/xsp/library/java/request.xsl"
> />
> </language>
> </library>
> </processor>
>
> Hmm. that's much nicer. The rest of the the configuration file can be
> rewritten as XML similarly. Anyone have any significant objections and/or
> suggestions for rewriting cocoon's properties file in XML?
I had this in plan for 2.0 but if you want to do it sooner, I'm ok for
it.
> Alternately,
> does anyone have any alternate syntax suggestions for associating
> namespace URIs with library URIs keeping the old properties file style
> syntax?
Ok, what about (having XML-based configs)
<processor name="xsp">
<library>
<language name="java"
<namespace uri="http://www.apache.org/1999/XSP/Request">
<resource location="classpath"
path="org/apache/cocoon/processor/xsp/library/java/request.xsl"
/>
</namespace>
<namespace uri="http://myownstuff">
<resource location="file"
path="/home/mystuff/lib/mystuff.xsl"
</resource>
</namespace>
</language>
</library>
</processor>
Hmmm, maybe too verbose... any comment?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
Changing XSP taglib namespace configuration behavior
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 2 Feb 2000, Stefano Mazzocchi wrote:
> Donald Ball wrote:
> >
> > On Mon, 31 Jan 2000, Stefano Mazzocchi wrote:
> >
> > > Meanwhile, I'll reply to the XSP questions, but when they deal with
> > > implementation details, I just don't know more than you do.
> > >
> > > Anyway, if you find something you don't like, you know the golden rule:
> > > fix it yourself! :)
> >
> > Me, I'm _trying_ to, but no one has voted on my proposal, so I'm just
> > cooling my heels right now.
>
> I vote +1 to your previous proposal.
>
> Also, could you please try to come up with a solution that doesn't
> require us to set a specific URL handler but that doesn't require you to
> change the configurations out of the box?
hmm. i'm not 100% sure i understand the desired constraints here. I think
what you're saying is that you want me to come up with a solution that
lets you map namespace URIs to .xsp files without using the resource://
URL? No wait, that doesn't make sense. What exactly do is the problem
we're trying to solve?
Anyway, what I'm thinking is that we should change the cocoon.properties
file so that instead of hardcoding prefixes like so:
processor.xsp.library.request.java =
resource://org/apache/cocoon/processor/xsp/library/java/request.xsl
we hardcode the URIs instead:
processor.xsp.library.java = http://www.apache.org/1999/XSP/Request|resource://org/apache/cocoon/processor/xsp/library/java/request.xsl
more descriptively:
processor.xsp.library.java = namespaceURI|xspURI
hmm. that syntax is atrocious. maybe it's time that we XMLized the
cocoon.properties file:
<processor name="xsp">
<library>
<language name="java"
<namespace
uri="http://www.apache.org/1999/XSP/Request"
lib="resource://org/apache/cocoon/processor/xsp/library/java/request.xsl"
/>
</language>
</library>
</processor>
Hmm. that's much nicer. The rest of the the configuration file can be
rewritten as XML similarly. Anyone have any significant objections and/or
suggestions for rewriting cocoon's properties file in XML? Alternately,
does anyone have any alternate syntax suggestions for associating
namespace URIs with library URIs keeping the old properties file style
syntax?
- donald
Re: FW: Redirecting users in Cocoon
Posted by Stefano Mazzocchi <st...@apache.org>.
Donald Ball wrote:
>
> On Mon, 31 Jan 2000, Stefano Mazzocchi wrote:
>
> > Meanwhile, I'll reply to the XSP questions, but when they deal with
> > implementation details, I just don't know more than you do.
> >
> > Anyway, if you find something you don't like, you know the golden rule:
> > fix it yourself! :)
>
> Me, I'm _trying_ to, but no one has voted on my proposal, so I'm just
> cooling my heels right now.
I vote +1 to your previous proposal.
Also, could you please try to come up with a solution that doesn't
require us to set a specific URL handler but that doesn't require you to
change the configurations out of the box?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------