forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: Extending DTD catalog in plugins
Date Tue, 01 Mar 2005 09:24:44 GMT
Ross Gardler wrote:
> David Crossley wrote:
> >Ross Gardler wrote:
> >>Since I am not very clued in with catalogs and their use I have no 
> >>opinion on this thread, but I do need to implement something. So, if 
> >>someone has the time (and the wine) to design a solution for *exactly* 
> >>the problem described in the above thread then I will implement it 
> >>(remember Sean does make a proposal that is discussed without a 
> >>conclusion, so this may be a shorter job than you think).
> >
> >This was sparked today by your message to users@ list. Assuming that
> >the CatalogManager.properties works for you, then this is not an
> >urgent issue.
> 
> Actually it is (although not necessarily a blocker for 0.7). There are
> many plugins that cannot be built using the current system. Basically,
> anything requiring a DTD. The CatalogManager.properties solution doesn't
> work for WAR files since the path to the catalog has to be a full path
> rather than a relative.

Sorry, i don't understand that. Why does it need to be a full path?
--David

> >I added an entry to Jira: http://issues.cocoondev.org/browse/FOR-451
> >so we can review the use of Catlog Entity Resolver later. I, for one,
> >do not have time prior to the upcoming 0.7 release. Anyway, i reckon
> >that it would be a big risk to mess with that stuff at this stage.
> 
> Yes, I agree, we will visit after 0.7, I hoped that there would be
> something simple we could do for plugins before that release. The only
> plugin currently affected is the simple-Docbook plugin, if we leave the
> DTD's in core as they are now it will work for 0.7
> 
> Ross

Mime
View raw message