If you're migrating to Struts 1.2, make sure you update all your DOCTYPEs. I believe I once had a problem where I was mixing a few DOCTYPEs and that didn't work so well.
Also, if the web container cannot find the DTDs, it may be because your DOCTYPE is wrong. This happened to me. This is the DOCTYPE I use: <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.2//EN" "http://struts.apache.org/dtds/struts-config_1_2.dtd";> Thanks, Paul -----Original Message----- From: Tim [mailto:[EMAIL PROTECTED] Sent: Friday, January 21, 2005 3:16 PM To: Struts Users Mailing List Subject: Re: Referencing the Local DTD rather than the http:// one that would be great, but couldnt figure it out. I've included struts.jar in the WEB-INF/lib but still doesnt solve it. is there anything else needs to be done? ----- Original Message ----- From: "Niall Pemberton" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <user@struts.apache.org> Sent: Friday, January 21, 2005 8:40 AM Subject: Re: Referencing the Local DTD rather than the http:// one > Why do you need to have local copies of these DTDs in the WEB-INF? Whats > wrong with just letting struts pick the "standard" DTDs shipped in the > struts.jar? > > Niall > > ----- Original Message ----- > From: "Lukas Bradley" <[EMAIL PROTECTED]> > To: <user@struts.apache.org> > Sent: Friday, January 21, 2005 3:52 PM > Subject: Re: Referencing the Local DTD rather than the http:// one > > >> What I find particularly annoying about this problem is references to >> local Struts Configuration files work correctly, which in turn load the >> Tiles Definitions. >> >> /WEB-INF/struts-config.xml >> /WEB-INF/tiles-defs.xml >> /WEB-INF/dtd/(all here) >> >> An example of my Struts Config definition, that works correctly: >> >> <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD >> Struts Configuration 1.2//EN" "file:///dtd/struts-config_1_2.dtd"> >> >> Which loads Tiles definitions: >> >> <plug-in className="org.apache.struts.tiles.TilesPlugin"> >> <set-property property="definitions-config" >> value="/WEB-INF/tiles-defs.xml" /> >> >> Which will not parse correctly with any of the following: >> >> <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Tiles >> Configuration//EN" "file:///dtd/tiles-config_1_1.dtd"> >> <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Tiles >> Configuration//EN" "file:///WEB-INF/dtd/tiles-config_1_1.dtd"> >> <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Tiles >> Configuration//EN" "file:///./dtd/tiles-config_1_1.dtd"> >> <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Tiles >> Configuration//EN" "file:///./WEB-INF/dtd/tiles-config_1_1.dtd"> >> >> As Tim stated in his post, absolute path references work correctly. >> However, this becomes tedious when migrating lots of configuration files >> between local filesystems and production ones. >> >> Any help appreciated. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. ------------------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
