Wiki source code of Pesky WOComponent Errors
Last modified by Ray Kiddy on 2008/08/23 17:18
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | The easiest way to get rid of these errors, when they are not really errors, is to use a "~/~/VALID" modifer on the tag. For example, if I have an EOEnterpriseObject named 'foo' and it will return a string from "someAttribute", then the tag below may cause a red error indicator to be displayed in eclipse, with the associated error text being: "There is no key 'someAttribute' for the keypath 'foo' in <component name>". |
| 2 | |||
| |
3.1 | 3 | <wo:str value="$foo.someAttribute" /> |
| |
1.1 | 4 | |
| |
3.1 | 5 | The tag below will cause eclipse to not display this error. |
| |
1.1 | 6 | |
| |
3.1 | 7 | <wo:str value="$foo.someAttribute~/~/VALID" /> |
| |
1.1 | 8 | |
| |
3.1 | 9 | One may also change this behavior by chaging the values in Eclipse -> Preferences -> WOLips -> 'Binding Validation and Binding Validation Rules'. (How? TBD) |