Thomas Dudziak <tomdz <at> first.gmd.de> writes: > > I'm behind a proxy, so that's probably the deeper reason for the fail. But > > as I know the generation works from the OJB tests I had a look into its > > schemas and there another DTD is referenced: > > http://db.apache.org/torque/dtd/database_3_0_1.dtd > > This one is probably not fetched from remote, but from a JAR, so it works. > > The OJB XDoclet module should also reflect that change. Otherwise I can not > > use it for my automatic build as I have to replace the DTD by hand. > > No you don't as you can specify the DTD that is used via the dtdUrl > attribute of the torqueschema subtask (see the docs for details).
Thanks for the hint, it works. > Any > other problem is due to Torque then (the XDoclet module does not check the > DTD), or the XML parser used by Torque (there are issues with older Xerces > parsers). That was clear to me. But Torque must have been failing as the wrong DTD was referenced and the XDoclet module added the reference to the schema file. That was why I wrote to this list. I don't know why the default is still http://jakarta.apache.org/turbine/dtd/database.dtd when Torque has moved to db.apache.org. This would also be the reason that Torque itself knows the database.dtd from db.apache.org, but not from jakarta.apache.org. Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
