Excellent insight! Since my problem was occurring during processing of the tutorials, I downloaded database.dtd and placed it under
$JETSPEED/tutorial/src/schema/dtd/database.dtd
then modified $JETSPEED/tutorial/src/schema/tutorial-schema.xml so it's DTD reference was the relative url
"src/schema/dtd/database.dtd"
The extended relative path was used since it apparently needs to be relative to the directory from which the maven command was issued...
Bada-boom, bada-bing! The tutorials now build!
I've also done the same modifications for the regular jetspeed build (both for database.dtd and database_3_1.dtd referred to in the various $JETSPEED/src/torque-schema/*-schema.xml files) to avoid intermittent failures in the future.
Thanks much for the troubleshooting info.
Cheers, Dan
Raphaël Luta wrote:
Given the issues you describe, I'd say it's related to the DTD validation of the torque schema files.
To avoid the issue, you can try the following: - download manually the DTD file http://jakarta.apache.org/turbine/dtd/database.dtd - put it in src/torque-schema - change the DTD reference in the xml files to "database.dtd"
It should work. If it doesn't want to use relative dtds, put the dtd on a local webserver (eg Tomcat) and modify the URL accordingly.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
