In addition to the previous email, while I am investigating this issue a bit I was curious:
Is the XML/DTD validation done with Local or Remote (web based) dtd docs?
It seems like the DTD's are located here
Can the DTDs be made local?
So I will be giving this a try tonight or over the weekend...However, I wanted to ask a couple of more questions:(just to start people thinking...)1. I would ultimately like to have a solution that requires only modifications to my website data, not changes to the Forrest XSL Files.Therefore, can we design/architect a change that can be contributed back to Forrest.2. Most users would want tracking, but they may not want the "Google" proprietary tracking,Therefore, is it possible to design it to accept a "CDATA" as aposed to a "PCDATA" thus allowing Arbitrary code in the website data.3. Is it possible to update the DTD Docs with optional fields. I Kinda like the validation.Bryce
On Fri, Sep 24, 2010 at 10:43 AM, Steve Wolke <email@example.com> wrote:
You can turn off validation of the skinconfig.xml in the forrest.properties file like the following
# validation properties
# This set of properties determine if validation is performed
# Values are inherited unless overridden.
# e.g. if forrest.validate=false then all others are false unless set to true.
Then to get your property you can just call