David Crossley wrote: > Michael Hartle wrote: <snip/> > > 2.) After adding the OpenOffice DTD to the catalog and trying to > > validate a content.xml with corresponds to the office.dtd, I encountered > > the bug that whenever entities are to be resolved, the ISO*.pen files > > are being searched in the same directory where the XML file to be > > validated is located. > > This indicates to me that the whole entity resolver is not working. > Are you sure that you have the catalog correctly configured? > Raise the resolver parameter verbosity=3 in cocoon.xconf to see. > > I am currently updating my 2.0 working copy and will check myself. > I was sure that i tested stuff after committing Christian's patch. > Let us pray that Bug 5060 (platform-specific problems with file:) > has not crawled back to life. > --David
I just checked 2.0 and all is OK for me. > Michael continued: > > After reverting a recent change to > > org.apache.cocoon.components.resolver.ResolverImpl.java submitted by > > Christian Schmitt (see > > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100691270713121&w=2), > > this issue was solved and any XML content produced by OpenOffice has > > successfully been validated so far. > > > > Has anyone seen such behavior too, or is it just me ? I am using a clean > > Cocoon 2.0 release build with extensions like new generators, source > > factories and the like which are closely modelled after existing > > components. I have no problems. It works for me without reverting that patch. It also works if i do revert the patch. This is a Linux platform. If you are sure that your catalog is configured properly, then please look at Bugzilla Bug #5060 to see if that is the problem. If you are not sure about your configuration for your new DTD, then please outline your steps. --David Crossley --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
