I'd guess the reason is to make it easier to keep the client- and
server-side validation in sync. java.net.URL is, obviously, not available
to the client-side validation. The Commons Validator list is probably the
right place to follow this up.
L.
Marc Logemann wrote:
Hi,
after looking into the code of UrlValidator and moreover looking into a
similar class in Tapestry which is no longer active as it seems, i
wonder why commons-validator UrlValidator is using Regex so much.
Wouldnt it be enough to just use java.net.URL and let this class do the
verification? Of course i am not quite sure how it deals non-schema URLs
but for complete URLs to verifiy, its perhaps a better choice.
Perhaps this one is for the developer list but i try it here first ;-)
Lindholm, Greg wrote:
I encountered this awhile back but didn't have time to investigate.
As a workaround I use the localhost IP address "127.0.0.1" but it
would be nice to get this fixed.
-----Original Message-----
From: Marc Logemann [mailto:[EMAIL PROTECTED] Sent: Thursday, July
28, 2005 8:33 AM
To: user@struts.apache.org
Subject: UrlValidator
Hi,
can it be that UrlValidator from Commons-Validator doesnt validate
URLs with localhost in it?
The following URL -> http://localhost:8081/context/jsp/versand_1.jsp
--
Laurie, Open Source advocate, Java geek and novice blogger:
http://www.holoweb.net/laurie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
