There's a bigger problem here. During normal Tapestry operation network requests will never be made for the DTD's, the SpecificationParser is hardwired to pull them from the Tapestry jar.
Are you running some external tool that needs the DTDs? Geoff On 6/27/06, Norbert Sándor <[EMAIL PROTECTED]> wrote:
Not a bad idea, thanks! :) Let's suppose that the component is used on many customer sites, and my company site is not available. I'm in the same situation. What I want is to completely disable XML validation in producion environment to avoid such errors. Regards, Norbi Andreas Bulling wrote: > On 27. Jun 2006 - 19:40:01, Norbert Sándor wrote: > | Hello! > | > | Sometimes the jakarta site is not accessible, in such cases I get the > | following exception: > | > | Unable to parse file:/blablabla.script: Connection timed out: connect > | java.net.ConnectException > | Connection timed out: connect > | http://jakarta.apache.org/tapestry/dtd/Script_3_0.dtd > > IMO it should be possible to copy the DTD from the jakarta server > to your local one and change the xml files appropriately. > Please correct me if I'm wrong... ;) > > Regards, > Andreas > > --------------------------------------------------------------------- > 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]
-- The Spindle guy. http://spindle.sf.net Blog: http://jroller.com/page/glongman Other interests: http://www.squidoo.com/spaceelevator/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
