Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Norbert Sándor
No external tool is used... Geoff Longman wrote: 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? G

Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Geoff Longman
Yes, the hardwiring of the parser is based on the publicid so if you get that messed up a request will go over the network. Mess up the ""-//Apache Software Foundation//Tapes..." part that is. If you mess up that *and* the url part...well your're just hosed. :-) Geoff On 6/27/06, Ryan Cupr

Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Ryan Cuprak
Actually we ran into this problem as well. I just checked with my coworker - as far as she can remember she made a mistake on the component specification (copy/paste probably). Once it was corrected it no longer tried to fetch the file Regards, Ryan On Tuesday, June 27, 2006, at 12:01PM,

Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Geoff Longman
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]

Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Konstantin Ignatyev
It seems to be better to register custom EntityResolver http://www-128.ibm.com/developerworks/library/x-tipent.html http://cocoon.apache.org/2.1/userdocs/concepts/catalog.html http://xml.apache.org/commons/components/resolver/ Norbert S�ndor <[EMAIL PROTECTED]> wrote: Not a bad idea, thanks! :)

Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Norbert Sándor
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

Re: xml parse error if the jakarta site is not accessible

2006-06-27 Thread Andreas Bulling
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

xml parse error if the jakarta site is not accessible

2006-06-27 Thread Norbert Sándor
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 Is there a way