Question on component cache

Question

I have built a component that wraps a standard button component. Based on some criteria, it enables/disables the button it wraps.
In my JSP A.jsp,
<s:myComp userName="">
<h:commandButton disabled=false>
</hx:commandExButton>
</s:myComp
In the encodeChildren method of my custom component,
if( component instanceof HtmlCommandExButton ) {
if( some condtion) {
System.out.println(" Is button disabled "+ ((HtmlCommandExButton)component).isDisabled);
//If button is enabled, disable it.
((HtmlCommandExButton)component).setDisabled(true);
Scenario:
1) I go to page A. My custom component disables the button by calling setDisabled method
2) I go to a different page and then come back to page A in the same session
3) My custom component reads the button's disabled property as true even though the disalbed is set to false in the JSP.
At step 3, I guess it gets the button component from the component tree cache. I have a few questions.
1) Is it a good idea to modify the properties of the enclosing components ?
2) How can I make my component read the real data instead of the cached data for the the enclosing components ?
3) Is it possible to evaluate the expression bound to disabled property to get the correct value ?

Answer 1

Hi RaymondDeCampo
Thanks for the reply. I am not holding the component in the session. It is actually the custom component's encodeChildren method where the child component is passed to it (In my case it is the button). First time when I visit the page, custom component reads the attributes of the child component and modifies them but the modified values will be retained even if I navigate around and come back to the same page.
HOw can I force JSF to get a fresh instance of the component ?
I am using IBM JSF1.1