cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@indexgeo.com.au>
Subject RE: Finishing Deprecation Package
Date Fri, 14 Mar 2003 08:23:10 GMT
Carsten Ziegeler wrote:
> David Crossley wrote:
> > Carsten Ziegeler wrote:
> > > I just fixed some bugs in the catalog resolving code; as far
> > > as I can tell everything is working fine. If you experience
> > > problems, just let me know.
> > 
> > Most bits seem to be working again, e.g. main Cocoon documentation.
> > I also resurrected the 'catalog-demo' sample and that works.
> > 
> > However other bits are still broken. The "Simplified DocBook"
> > sample is busted. The old ResolverImpl.java used to load an
> > additional catalog via the "local-catalog" parameter of
> > cocoon.xconf using a full filesystem pathname starting with "/"
> > ... now that is busted and the resolver tries to incorrectly
> > load it from .../cocoon-2.1/build/webapp/home/me/work/...
>                                       ^^^^^
> Uh, that's not nice. The default catalog is defined by "/WEB-INF/...."
> and this is loaded from the context directory.
> Now, you say that if I define the "local-catalog" with "/..." then
> this should *not* be loaded from the context directory, but
> it should be assumed that this is an absolute path, right?

Yes. And that is how it has always worked in the past.
Remember too that the entity resolver deals with the pathname
itself, and it expects a platform-independent pathname as
described in CatalogManager.properties (i will tweak the
cocoon.xconf description to match that).

> Now, there is something wrong with this approach. We can easily
> change (which should be the 'correct' solution) that a path
> starting with "/" is treated as an absolute path. So
> if you want to load from the context directory, you have
> to specify "WEB-INF/.." instead of "/WEB-INF".

When i was investigating these issues today, i commented the
same to myself.

> But using a starting "/" with two different behaviours is imho
> too confusing.
> What do you think? Changing the above is absolutely simple.

I agree - let us do it. I will note this in changes.xml later,
though it should not affect too many people as this is
only for over-riding the default Cocoon catalog.

> Or did I oversee something?

Well the thing that really worries me is the hell that we
went through last time with getting consistent behaviour
on all platforms.

--David




Mime
View raw message