>From: "Dan Diodati" [EMAIL PROTECTED] >I was creating a custom jsf component to use and I noticed that the component >instance that is passed to the renderer decode method is different than the >one passed to the encodeBegin,encodeEnd. > >This seems to be a bug since I want to be able to set some values taken from >outside params onto the component within the decode and later in the >encodeBegin access the component with the updated values. > >Currently the component loses the values set on it due to the component >instance being different when the encodeBegin is called. > >Is this a bug in the myfaces implementation? >
This is not a bug. It's just the way that JSF works. You most might need to implement these methods in your component. public Object saveState(FacesContext context) public void restoreState(FacesContext context, Object state) Section 2.5.3.1 - State Management Considerations for the Custom Component Author in the JSF 1.1 spec talks about this issue. You might also take a look at some of the other components out there: http://svn.apache.org/viewvc/myfaces/core/trunk/api/src/main/java/javax/faces/component/UIInput.java?view=markup >Dan Gary
