Dynamic rendered component doesn't appear in source file! How to get hold

Question

I have three select components on my page, the 1st one is selectOneRadio2, the 2nd one is selectManyCheckbox1, and the 3rd one is selectOneRadio3. The selectManayCheckbox1 and selectOneRadio3 do not display at the same time. Their rendered properties are dynamically set in the managed bean depending on the choice of the selectOneRadio2. It toggles between those two components just fine when I set the rendered property in the managed bean dynamically in a value change event, however when I tried to retrive the value from the 3rd component selectOneRadio3 which was not rendered initially (or by default), I get nothing. When I viewed the source file after the component is rendered on the page, that component is not in the source file at all, and I saw the default rendered 2nd component (selectManyCheckbox1) instead!!! How can I get hold of the later rendered component (selectOneRadio3)???
<tr:selectOneRadio value="#{bindings.expenseTypeList1.inputValue}"
label="Expense Type"
binding="#{backing_eef_expense.selectOneRadio2}"
id="selectOneRadio2"
valueChangeListener="#{backing_eef_expense.expenseTypeChange}"
autoSubmit="true">
<f:selectItems value="#{bindings.expenseTypeList1.items}"
binding="#{backing_eef_expense.selectItems2}"
id="selectItems2"/>
</tr:selectOneRadio>
<tr:panelGroupLayout binding="#{backing_eef_expense.panelGroupLayout3}"
id="panelGroupLayout3"
partialTriggers="selectOneRadio2">
<tr:selectManyCheckbox label="Multi Choice"
rendered="#{backing_eef_expense.renderMultiChoice}"
binding="#{backing_eef_expense.selectManyCheckbox1}"
id="selectManyCheckbox1"
valuePassThru="true">
<f:selectItems binding="#{backing_eef_expense.selectItems4}"
id="selectItems4"
value="#{backing_eef_expense.itemList2}"/>
</tr:selectManyCheckbox>
</tr:panelGroupLayout>
<tr:panelGroupLayout binding="#{backing_eef_expense.panelGroupLayout4}"
id="panelGroupLayout4"
partialTriggers="selectOneRadio2">
<tr:selectOneRadio label="Single Choice"
rendered="#{!backing_eef_expense.renderMultiChoice}"
binding="#{backing_eef_expense.selectOneRadio3}"
id="selectOneRadio3" valuePassThru="true">
<f:selectItems binding="#{backing_eef_expense.selectItems3}"
id="selectItems3"
value="#{backing_eef_expense.itemList2}"/>
</tr:selectOneRadio>
</tr:panelGroupLayout>
I use Trinidad components because it's a migrated application from 10g to 11g. I'm using 11g now.
Edited by: SophiaM on Feb 3, 2011 10:23 AM

Answer 1

Hi Joonas, Thank you for your replay. I don't know the answer to your question.
First, I have no idea if that will cause any problem, or the libraries would have conflict or not if I use both within the same application. We are very careful about that becaue we had a lot trouble when we did the migration. A LOT of things were broken after the migration and some of the issues were caused by conflict on libraries. That's why although I am creating new pages in the application, I still carefully stay with Trinidad components.
Second, out of curiosity from your suggestion, I tried to add ADF library and technology into my project, I still don't see the ADF components avaiable in my Component Palette panel, even after I restarted JDeveloper. So I don't know how to switch it even if I dare.
I just read something like this, seems apply to my situation:
Your correct in the fact that rendered=false is useless. However, that is not how it's typically used. Typically this will be bound to a backing bean which will allow you to turn the component on/off. You should use a hidden input field and a switcher if you need to keep the value in the form submission. Adam is totally correct in that it will break a bunch of stuff if we all of a sudden just "turned it on" because people have come to expect the current behavior.
Do you know what a switcher is?