Extending DTD catalog in plugins

[Ross Gardler <ro...@gardler.org>]

I have a need in one of my plugins to add some DTD's to Forrest. This 
issue raised its head some time ago with Sean Wheller's proposal for a 
full Docbook plugin, as a result there was a long discussion (which gets 
interesting from 
http://marc.theaimsgroup.com/?l=forrest-dev&m=109894335305317&w=2 onwards).

The end result of this discussion was:

--- Start Quote ---

On Thursday 28 October 2004 12:27, David Crossley wrote:
 > > Do you see the benefit above?
 >
 > I think so. I will go mull it over with some
 > late-night card game and wine.

Good idea. No rush. Do however consider that now we have plugins, the
locations will change and this method becomes more of a necessity. Take 
the Docbook Plug-in as example.

--- End Quote ---

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).

Ross

Re: Extending DTD catalog in plugins

[Ross Gardler <rg...@apache.org>]

David Crossley wrote:
> 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?

Not sure why it needs it but I made this statement because:

The instructions on 
http://forrest.apache.org/docs/validation.html#catalog say:

"Next specify the full path to your catalog.xcat in the 
src/documentation/classes/CatalogManager.properties file."

In addition the sample properties file provided in the site I was 
working on said I could only use absolute paths. However, in opening the 
file in the current SVN head of fresh-site I notice this has changed and 
a new property has been added "relative-catalogs=no".

So we just need to update the docs accordingly (I'll do it now).

The solution is still no good for plugins (at least as I understand it) 
since they cannot provide a CatalogManager.properties file to the 
project. I'm OK with revisiting this after 0.7 though, you've given me 
enough to get my current project working with a hack - that's all I care 
about in the short term.

Thanks,
Ross

Re: Extending DTD catalog in plugins

[David Crossley <cr...@apache.org>]

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

Re: Extending DTD catalog in plugins

[Ross Gardler <rg...@apache.org>]

David Crossley wrote:
> Ross Gardler wrote:
> 
>>I have a need in one of my plugins to add some DTD's to Forrest. This 
>>issue raised its head some time ago with Sean Wheller's proposal for a 
>>full Docbook plugin, as a result there was a long discussion (which gets 
>>interesting from 
>>http://marc.theaimsgroup.com/?l=forrest-dev&m=109894335305317&w=2 onwards).
>>
>>The end result of this discussion was:
>>
>>--- Start Quote ---
>>
>>On Thursday 28 October 2004 12:27, David Crossley wrote:
>>
>>>>Do you see the benefit above?
>>>
>>>I think so. I will go mull it over with some
>>>late-night card game and wine.
>>
>>Good idea. No rush. Do however consider that now we have plugins, the
>>locations will change and this method becomes more of a necessity. Take 
>>the Docbook Plug-in as example.
>>
>>--- End Quote ---
>>
>>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.

> 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

Re: Extending DTD catalog in plugins

[David Crossley <cr...@apache.org>]

Ross Gardler wrote:
> I have a need in one of my plugins to add some DTD's to Forrest. This 
> issue raised its head some time ago with Sean Wheller's proposal for a 
> full Docbook plugin, as a result there was a long discussion (which gets 
> interesting from 
> http://marc.theaimsgroup.com/?l=forrest-dev&m=109894335305317&w=2 onwards).
> 
> The end result of this discussion was:
> 
> --- Start Quote ---
> 
> On Thursday 28 October 2004 12:27, David Crossley wrote:
> > > Do you see the benefit above?
> >
> > I think so. I will go mull it over with some
> > late-night card game and wine.
> 
> Good idea. No rush. Do however consider that now we have plugins, the
> locations will change and this method becomes more of a necessity. Take 
> the Docbook Plug-in as example.
> 
> --- End Quote ---
> 
> 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.

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.

--David