Brian M Dube wrote: > > > > FOR-1172 - enable validation of the internal xml > > > > FOR-1173 - add demonstration of using xml source documents > > without declaring a DTD > > This looks good. Is the idea to replace the Ant target with pipeline > validation?
I don't know. I like the fact that the intermediate xml is not validated, because one can cram all sorts of non-xdoc elements into the pipeline. e.g. try doing localhost:8888/samples-b/embedded_html.validation.xml Perhaps we could find a way to exclude certain documents from validation (or from the final report). I wonder how such validation could operate. When we do 'forrest site' it provides Cocoon a "start-uri" to commence from. Cocoon appends any other new URIs that it finds during its crawl. It generates the *.html files, etc. Perhaps we can also get it to generate a "*.validation.xml" for each URI too. Then after Cocoon finishes, an Ant target might post-process all such files and summarise them into one large report. Then tidy up to remove all those files, because we don't want them to be deployed as part of the site. Do you have some ideas? -David
