George wrote: > Well, this looks better :) however, right now I cannot see > how we could use specific messages with the general integer > translator. Integer translator is the first one that is > getting called in this validation chain and it will throw > it's own validation error. If there is no issue with > translating the given value to an int then the filed > validators will be applied. > > So right now we are displaying messages like: > > 4 --> "Proxy Keepalive Time cannot be less than 5." -> > field validation > > 2000001 --> "Proxy Keepalive Time cannot be greater than > 2000000." -> field validation > > 2010fun or 200000000000 --> "Proxy Keepalive Time must be > numeric." -> this one is thrown by integer validation
Ah, I see. Being larger than 2000000 cannot be detected as the problem, because 200000000000 cannot even be recognized as a number. That's too bad, but we can certainly live with it. Thanks. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
