Its not recommended that you use JSTL with JSF (RI or MyFaces.) Things are changing in the upcoming JSF spec but that is a long ways off.
As for your original problem, I assume you are not using "tabbed pane" or any complicated container for your components. Are you sure its not a problem with your navigation rules? If you are lacking an "action" attribute on your commandButton then you will end up on the same page (that could be one explanation.) Not sure what to make of those warnings. They seem to indicate that your bean (transLocaleBean) is not defined in faces-config.xml. I can't be sure without checking the source code but that is my guess based on how JSF works in general. Generally the VariableResolver comes into play when evaluating an EL expression in a JSF page. If the bean was defined but did not yet exist, JSF would create it for you (and not warn you) so hence my theory on it missing from your config. sean On 5/20/05, Mikey E <[EMAIL PROTECTED]> wrote: > So since the panelGrid continues to not work correctly for me, I > thought I would just use a <c:forEach> instead (to iterate over my > collection of beans) and then embed a <h:form> within the body. I > tried this and set the loop's current bean into the session within the > loop body. I then used the jsf form components to retrieve the bean > from the session & write out the form values. This works fine for the > first loop but jsf tags use the initial bean value in the subsequent > loops, even though my jstl tags (used only for testing) use the > correct bean as expected. So it looks like the jsf tags aren't picking > up the bean when it's changed. > > So my workaround failed (which sucks) but if the correct components > were processed in the first place, I wouldn't have had any of these > problems (and wouldn't have wasted 3 days & counting). > > > If this wasn't a long weekend for me, I think I would freak out.. >
