Rembember that this is a performance improvement which should have no functional impact whatsoever.
Well, it is not only performance really. There are two issues. One is performance, the other is that the URL constructor requires registered handlers and only a few of them are available per default (see also HV-886). A regular expression would also get by the "protocol problem".
If we go down the configuration way, then there is also the BV compliant approach. You can always use a mapping file and constraint-definition do exclude the default URL validator and provide a own one. All we needed to do is to provide a regexp based URL constraint validator and leave it to the user to enable it. No further changes required from our side, except maybe some documentation.
|