Ulrich Teichert a écrit :
>
>
> Uh-oh. That's a bit hard - how do I know which property really is required?
> I thought that when it's required and missing, I would get a "method not
> found" exception...
>
Sorry, was not clear. I meant, when you programmatically create a
Component X with application.createComponent("X"), ensure that all X
properties that are marked as required by the corresponding X taglib
have been set.
(for example, HtmlInputText as 2 required properties: id and value).
I never meant to add methods to your bean :) I just meant to ensure your
UIComponent getXXXX() {... } was doing all required initialisation steps
for every component it has created.
>
>> 4) it still fails with only 1 binding, and no nested panelGrid.
>>
>
> I've tried whithout the nested panelGrid, did not help either. I wasn't
> able to strip it down to one binding only and still perform something
> usefull. What did you wanted to test in that case?
>
Wanted to check there was no bug with embedded panelGrids and that there
was no problem with the fact your bean seems to have 2 dependents on
each other components.
> CU,
> Uli
>
>
That's all i have in my mind as solution, quite poor :) Sorry!
