It seems to me that you’re putting more effort into this than it warrants. Consider: If your purpose is to guard against mis-entered phone numbers, then you can probably catch well over 90% of them with just a very simple check. If your purpose is to try to force users to provide a valid number … Read more
I think you have two problems here. Keeping validation errors through a redirect Repopulating the form fields so the user doesn’t have to enter all the information again. Both of these things are connected. Validation errors are usually displayed through the error_msg_for method which acts on an object. Usually provided by the controller as the … Read more
I believe there are three different cases that you have to worry about: strings (anything that requires quotes): ”” + replace(@string, ””, ”””) + ”” names (anything where quotes aren’t allowed): quotename(@string) things that cannot be quoted: this requires whitelisting Note: Everything in a string variable (char, varchar, nchar, nvarchar, etc.) that comes from user-controlled … Read more
You can resolve this using a lookahead assertion. Basically what we’re saying is I want a series of specific letters, (e, ex, ext, x, extension) followed by one or more number. But we also want to cover the case where there’s no extension at all. Side Note, you don’t need brackets around single characters like … Read more
The PrimeFaces ajax response puts an args object in the JS scope which has a validationFailed property. You could just check for that in the oncomplete. <p:commandButton … oncomplete=”if (args && !args.validationFailed) dialogaboutDEQ.show()” /> If you’re performing validation in action method instead of in a normal validator, and you can’t rework that, then you need … Read more
Often the use of self is to force Ruby to recognize that as a method call and not mis-interpret it as a variable. Without prior knowledge of a method called day=, then day = “x” looks to Ruby like a variable assignment. self.day = “x” is always a method call. The reason this is trouble … Read more
Unfortunately, neither the JDK bundled version (as of Java 8) nor the latest official version from maven central (2.11.0) contains XSD 1.1 implementation. You actually need the 2.11.0-xml-schema-1.1-beta version of Xerces to able to run the example in the FAQ you have linked. You may do one of the following. Download the Xerces2 Java 2.11.0 … Read more
Use this rexeg /\(?([0-9]{3})\)?([ .-]?)([0-9]{3})\2([0-9]{4})/ (123) 456 7899 (123).456.7899 (123)-456-7899 123-456-7899 123 456 7899 1234567899 supported
Have a look at strtol(), it can tell you about invalid parts of the string by pointer return. And beware of enthusiastic example code.. see the man page for comprehensive error-handling.
You can use :valid and :invalid selectors. Something like this .field:valid { border-color:#0f0; } .field:invalid { border-color:#f00; } However, this will only work in browsers that support native validation, and only for fields that make sense. As far as I know, right now that only means Chrome (maybe Safari, but haven’t checked). So by native … Read more