On 09/giu/07, at 15:19, Riccardo De Menna wrote:
> 2. The binding validation (omg validating ognl is so cool) is
> fantastic but what if I have some bindings that are not strong
> typed? Let's say for example a binding that points to
> parent.someCustomMethod. The validator claims parent has no such
> method but I know it does since at runtime it will. Can I inform
> the validator to skip that entry? Or can I cast it via ognl into
> the correct type to calm down the validator? The specific case of
> parent can be fixed by adding an pattern in the preferences to skip
> anything starting with "parent." but I came across other issues of
> the same problem on custom code.
> Same applies to some warnings about "collection" objects or even
> the..ount operator I use often. I know it's only a warning but can
> I still get warnings and disable them one by one? (This wod
> validation is so addictive I can't tolerate the idea of turning it
> off :-).
Oh ok I found the // VALID comment in Anjo's code... I knew there had
to be a way :P Is there some place where can I find some
documentation on these things? Other possible "comments"?
Ric
This archive was generated by hypermail 2.0.0 : Sat Jun 09 2007 - 09:31:22 EDT