commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17799] New: - '/' not escaped in regexp mask
Date Sat, 08 Mar 2003 00:24:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17799>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17799

'/' not escaped in regexp mask

           Summary: '/' not escaped in regexp mask
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Validator
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: dan@mojavelinux.com


If the delimiter for the perl regular expression is going to be hardcoded to be
'/' in the GenericValidator class, it would make sense that the regexp passed
into matchRegexp would have any instances of '/' automatically escaped.  This
way, in the validator.xml file, the developer would not have to worry about
attempting to escape characters based on an invisible regexp delimiter.  Even
more important, if a different regexp engine was used for the same validator.xml
file, irrelevant '/' escapes would not be present, or if the delimiter was
changed in the code.  I think that the developer need not know that delimiters
are even being used.

I would add this functionality in the getDelimittedRegexp() method.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message