Re: [Patch] A bit of help to get dtd out of the skinconf.xml file

[Juan Jose Pablos <ch...@che-che.com>]

Dave Brondsema wrote:
> 
> 
> Thanks for the support, but I've already done as much locally (and some more:
> update src/documentation/skinconf.xml,
> src/core/context/resources/schema/catalog).  And the version of skinconf will
> not be tied to the forrest version (your patch had v06)
> 
> Anyway.. when trying to run forrest I've had similar problems as I've noted at
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=10093
> and I've referenced this before.
> 


Can you forward you work on this issue?. I would like to test the use of 
xslt to resolve this.

Cheers,
Cheche

Re: [Patch] A bit of help to get dtd out of the skinconf.xml file

[Juan Jose Pablos <ch...@che-che.com>]

Dave Brondsema escribió:
> Unfortunately I lost my local changes a while ago (probably when 
> switching away from CVS).  I think what I did was:
> 
> Create a .dtd for <!DOCTYPE skinconfig
> PUBLIC "-//Apache Software Foundation//DTD Forrest Skin Configuration 
> 1.0//EN"
> "http://xml.apache.org/forrest/dtd/skinconf_1_0.dtd"> based on the 
> inline DTD.  (the version number will increment with every change to the 
> file)
> 

I will use
<public publicId="-//APACHE//DTD Skin Configuration V0.6//EN"
         uri="dtd/skinconfig-v06.dtd"/>
It looks more like the other forrest schema.

> 
> then I ran into problem #2 described at 
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=10093 
> 
> 

fine I will use xslt to move the result to build/webapp/skinconf.xml 
without the DTD information so it can be loaded by xmlproperty


Cheers,
Cheche

Re: [Patch] A bit of help to get dtd out of the skinconf.xml file

[Dave Brondsema <da...@brondsema.net>]

Juan Jose Pablos wrote:
> Dave Brondsema wrote:
> 
>>
>>
>> Thanks for the support, but I've already done as much locally (and 
>> some more:
>> update src/documentation/skinconf.xml,
>> src/core/context/resources/schema/catalog).  And the version of 
>> skinconf will
>> not be tied to the forrest version (your patch had v06)
>>
>> Anyway.. when trying to run forrest I've had similar problems as I've 
>> noted at
>> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=10093 
>>
>> and I've referenced this before.
>>
> 
> 
> Can you forward you work on this issue?. I would like to test the use of 
> xslt to resolve this.
> 
> Cheers,
> Cheche
> 

Unfortunately I lost my local changes a while ago (probably when 
switching away from CVS).  I think what I did was:

Create a .dtd for <!DOCTYPE skinconfig
PUBLIC "-//Apache Software Foundation//DTD Forrest Skin Configuration 
1.0//EN"
"http://xml.apache.org/forrest/dtd/skinconf_1_0.dtd"> based on the 
inline DTD.  (the version number will increment with every change to the 
file)

Set the skinconf.xml from fresh-site and src/documentation to use this 
doctype

remove the skinconf.rnc since validation will be against this versioned DTD

update build.xml (and forrest.build.xml too, I think) to use 
<xmlvalidate> instead of <jing> to validate skinconf files

then I ran into problem #2 described at 
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=10093

-- 
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal