Using the "parseClient" event, you could intercept the string submitted by the user and do the filtering before the value is assigned to a page property.
You could also design a translator for this purpose. On Fri, May 23, 2008 at 3:41 AM, Peter Stavrinides <[EMAIL PROTECTED]> wrote: > Hi All > > Can anyone offer suggestions on best practice for handling validation > specifically for preventing cross site scripting and code injection etc in > Tapestry applications. Is there anything built into the framework I could > use... if not what is the best way to plug something of my own in. What I > mean is should I write my own validator/s and use them in every form > component?, or is there a more elegant way I should know about, say a filter > or something? Does anyone use a 3rd party library written specifically for > this? > > Thanks > Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
