Re: Validator DTD - local resolution
On Thu, 5 Dec 2002, Frost, Gary [IT] wrote: Date: Thu, 5 Dec 2002 09:56:16 +1100 From: Frost, Gary [IT] [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: Validator DTD - local resolution Hi, I posted a message a few days ago about my validator not working, that a message was present in my logfile outputs saying that Jakarta.apache.org could not be resolved. Jorge Martins helped me out by telling me how to set up a proxy in my webserver (Tomcat 4) (-DproxySet=true, -DproxyHost=HOST -DproxyPort=PORT) which gets me out of immediate problems as now the webserver goes and downloads http://jakarta.apache.org/commons/dtds/validator_1_0.dtd http://jakarta.apache.org/commons/dtds/validator_1_0.dtd . However I don't consider this a permanent solution as we really really don't want this dependence. We should be able to resolve the dtd locally. I've checked my commons-validator.jar and the validator_1_0.dtd is there under org.apache.commons.validator.resources. And my webapp logfiles show that the commons-validator.jar is being loaded. Any ideas on why then the dtd cannot be resolved without going external? And how to fix it? IIRC this has already been fixed in the commons-validator code (there will be a 1.0.1 release of commons-validator soon because of this bug). But, if that's true, it means that the fix is present in recent nightly Struts builds, because they also take the most recent nightly build of each commons library that Struts depends on. Could you try it with, say, last night's nightly build? Thanks Gary Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Validator DTD - local resolution
Spot on, grabbed the 20021204 build of struts turned off the proxy, and all is fine and dandy. Thanks Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Thursday, 5 December 2002 11:23 AM To: Struts Users Mailing List Subject:Re: Validator DTD - local resolution On Thu, 5 Dec 2002, Frost, Gary [IT] wrote: Date: Thu, 5 Dec 2002 09:56:16 +1100 From: Frost, Gary [IT] [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: Validator DTD - local resolution Hi, I posted a message a few days ago about my validator not working, that a message was present in my logfile outputs saying that Jakarta.apache.org could not be resolved. Jorge Martins helped me out by telling me how to set up a proxy in my webserver (Tomcat 4) (-DproxySet=true, -DproxyHost=HOST -DproxyPort=PORT) which gets me out of immediate problems as now the webserver goes and downloads http://jakarta.apache.org/commons/dtds/validator_1_0.dtd http://jakarta.apache.org/commons/dtds/validator_1_0.dtd . However I don't consider this a permanent solution as we really really don't want this dependence. We should be able to resolve the dtd locally. I've checked my commons-validator.jar and the validator_1_0.dtd is there under org.apache.commons.validator.resources. And my webapp logfiles show that the commons-validator.jar is being loaded. Any ideas on why then the dtd cannot be resolved without going external? And how to fix it? IIRC this has already been fixed in the commons-validator code (there will be a 1.0.1 release of commons-validator soon because of this bug). But, if that's true, it means that the fix is present in recent nightly Struts builds, because they also take the most recent nightly build of each commons library that Struts depends on. Could you try it with, say, last night's nightly build? Thanks Gary Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Validator DTD - local resolution
I have posted the same problem in http://www.mail-archive.com/struts-user@jakarta.apache.org/msg50700.html To validate the fix in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14506 I had to disable my Windows 2K network connection (rather than removing the cable). The result is an error java.net.UnknownHostException: jakarta.apache.org when struts initializes validator plugin. Next I try to unplug the cable with network connection enable, everything is okie. Any advice on this? What I really concern here is the error message it self. java.net.UnknownHostException: jakarta.apache.org means struts tries to do a host to network translation. What happens if dns translation is disable? I have customer who is very strict on this. -Dan From: Frost, Gary [IT] [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Wednesday, December 04, 2002 5:30 PM Subject: RE: Validator DTD - local resolution Spot on, grabbed the 20021204 build of struts turned off the proxy, and all is fine and dandy. Thanks Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Thursday, 5 December 2002 11:23 AM To: Struts Users Mailing List Subject: Re: Validator DTD - local resolution On Thu, 5 Dec 2002, Frost, Gary [IT] wrote: Date: Thu, 5 Dec 2002 09:56:16 +1100 From: Frost, Gary [IT] [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: Validator DTD - local resolution Hi, I posted a message a few days ago about my validator not working, that a message was present in my logfile outputs saying that Jakarta.apache.org could not be resolved. Jorge Martins helped me out by telling me how to set up a proxy in my webserver (Tomcat 4) (-DproxySet=true, -DproxyHost=HOST -DproxyPort=PORT) which gets me out of immediate problems as now the webserver goes and downloads http://jakarta.apache.org/commons/dtds/validator_1_0.dtd http://jakarta.apache.org/commons/dtds/validator_1_0.dtd . However I don't consider this a permanent solution as we really really don't want this dependence. We should be able to resolve the dtd locally. I've checked my commons-validator.jar and the validator_1_0.dtd is there under org.apache.commons.validator.resources. And my webapp logfiles show that the commons-validator.jar is being loaded. Any ideas on why then the dtd cannot be resolved without going external? And how to fix it? IIRC this has already been fixed in the commons-validator code (there will be a 1.0.1 release of commons-validator soon because of this bug). But, if that's true, it means that the fix is present in recent nightly Struts builds, because they also take the most recent nightly build of each commons library that Struts depends on. Could you try it with, say, last night's nightly build? Thanks Gary Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
