string.jsp declares & uses the "transLocale" bean as the iterator variable in <h:dataTable>. Within the <h:dataTable>, a form action invokes TranslationBean (a managed bean declared in my config file) which brings the user to translation.jsp. This page then has a button & form which invokes TranslationBean again (but with different parameters).
string.jsp (the page with the datatable) displays correctly & the link works. My managed bean executes correctly and the correct page is displayed. Clicking on another link then gives me an error saying transLocale is null. This is the iterator bean from the previous page and is not referenced by the managed bean or the current jsf page. Just for kicks, I added the iterator bean to my config file and I no longer got the error. I haven't had to do this for other iterator beans and don't see where/how this bean should even be referenced (since it was from the previous page). When I was debugging the request previously, it looked as if the wrong children were being processed for the viewroot. Now that the bean is in the config file, I guess it just creates a new one when needed (even though it isn't really being used). On 5/24/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > I'm just using a simple <h:dataTable>. My nav rules & action look fine > > (very similar to my other pages that work correctly). That bean > > (transLocaleBean) is not defined within my faces-config.xml file > > because it is the value of the var attribute and is not a regular > > managed bean. It renders correctly, it just does not process the > > correct components when I submit. > > If your bean is not defined in faces-config.xml then why is JSF trying > to instantiate it? That is what the following log message seems to > indicate is happening: > > (66016 ms) [http-8080-Processor24] WARN : > org.apache.myfaces.el.VariableResolverImpl#resolveVariable : Variable > 'transLocaleBean' could not be resolved. > > I would suggest solving this riddle first. Its most likely related to > your problem although I can't see the connection offhand. > > sean >
