Would it be possible (and I'm not very familiar with Validations API) for it to validate not just Strings but anything extending CharSequence? I know Jsoup's looking for strings, but couldn't we call toString() on the object passed in?<br>
<br><div class="gmail_quote">On Sun, Jun 12, 2011 at 11:16 AM, George Gastaldi <span dir="ltr"><<a href="mailto:gegastaldi@gmail.com">gegastaldi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Ok, created a new pull request with the proposed changes:<br>
<br>
<a href="https://github.com/hibernate/hibernate-validator/pull/62" target="_blank">https://github.com/hibernate/hibernate-validator/pull/62</a><br>
<br>
Let me know if there is need of something more.<br>
<br>
Regards,<br>
<br>
George<br>
<br>
2011/6/12 Kevin Pollet <<a href="mailto:pollet.kevin@gmail.com">pollet.kevin@gmail.com</a>>:<br>
<div><div></div><div class="h5">> Hi all,<br>
><br>
> +1<br>
> I think it's useful to allow customization of the constraint. As said Shane<br>
> the annotation should provide an enum allowing to use all built-in JSoup<br>
> whitelist and allow the user to specify its whitelist implementation.<br>
> --Kevin<br>
><br>
> Le dimanche 12 juin 2011 à 13:14, Gunnar Morling a écrit :<br>
><br>
> Hi George,<br>
><br>
> I added some comments to your pull request.<br>
><br>
> With respect to Shane's whitelist suggestion you might have a value()<br>
> attribute accepting an enumeration with the standard whitelist<br>
> implementations and alternative attribute Class<? extends Whitelist><br>
> whiteListClass() which allows to specify custom whitelist classes.<br>
><br>
> --Gunnar<br>
><br>
><br>
> 2011/6/12 George Gastaldi <<a href="mailto:gegastaldi@gmail.com">gegastaldi@gmail.com</a>>:<br>
><br>
> Cool ideas. Will implement it ASAP<br>
><br>
> Em 12/06/2011, às 02:06, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> escreveu:<br>
><br>
> Looks good, although I wouldn't hard code Whitelist.basic() as the<br>
> default... instead I would make Whitelist.relaxed() the default, and then<br>
> perhaps allow the developer to override it by specifying an enum value for<br>
> the validation level allowed on the @WebSafe annotation. E.g:<br>
><br>
> // Default would use Whitelist.relaxed()<br>
> private @WebSafe String content;<br>
><br>
> // This would use the basic whitelist<br>
> private @WebSafe(basic) String content;<br>
><br>
> // Basic whitelist plus images<br>
> private @WebSafe(basicWithImages) String content;<br>
><br>
> It would even be nice to somehow allow the developer to specify their own<br>
> whitelist, if you can work out an elegant way to implement it.<br>
><br>
><br>
> On 12/06/11 12:46, George Gastaldi wrote:<br>
><br>
> Hey Shane,<br>
><br>
> I implemented the @WebSafe annotation you mentioned on Hibenate Validator.<br>
> The pull request is <a href="https://github.com/hibernate/hibernate-validator/pull/61" target="_blank">https://github.com/hibernate/hibernate-validator/pull/61</a><br>
><br>
> Regards,<br>
><br>
> George Gastaldi<br>
><br>
> _______________________________________________<br>
> seam-dev mailing list<br>
> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
><br>
><br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br>