Two possiblities.
1) Your pages are actually not generating the same ids for the
t:saveState components. You could check this by creating another
component next to them (like h:outputText) with a similiar id, and
verifying the fully-qualified client id path is the same for your test
component (since you can do a view source to check it).
2) Trinidad -- don't have enough experience with it to know if there's
something specific to Trinidad that affects how the saveState behavior
might change, ie, navigation or state saving. Seems unlikely, though.
On 4/20/07, Francisco Passos <[EMAIL PROTECTED]> wrote:
I've checked the code and no JSF tags are present.
I'm trying to navigate from page pesquisarFicha.jsf to page
consultarFichaImport.xhtml using the
<tr:commandButton text="Consultar"...>
In the first page I fill the inputField mapped to
#{pesquisaFichaBean.operador} with some value. When I reach the second page,
it is not.
I have the following navigation rule in my faces-config.xml:
<navigation-rule>
<from-view-id>/pages/ficha/pesquisarFicha.xhtml</from-view-id>
<navigation-case>
<from-outcome>consultarFichaImport</from-outcome>
<to-view-id>/pages/ficha/consultarFichaImport.xhtml</to-view-id>
</navigation-case>
</navigation-rule>
On 4/20/07, Mike Kienenberger <[EMAIL PROTECTED] > wrote:
> Sure. Post the code.
>
> The subtle facelets issue can be easily checked -- do a view source
> and make sure that you're not seeing unprocessed JSF tags in the
> output.
>
> On 4/20/07, Francisco Passos <[EMAIL PROTECTED]> wrote:
> > That's odd.
> >
> > I'm using the same id for the same bean, which is Serializable (I
changed
> > the non-serializable bindings - like CoreSelectOneRadio and such - to
> > transient, in order to keep serializability). I'm not using <redirect/>
as
> > well and although I am defining the t namespace in every page, it still
> > doesn't keep the state.
> >
> > Any further ideas? I can post the code if you'd like.
> >
> > Thanks,
> > Francisco Passos
> >
> >
> > On 4/20/07, Mike Kienenberger < [EMAIL PROTECTED]> wrote:
> > > - Using a different id for the same bean on two different pages.
> > > - Not correctly implementing Serializable or Stateholder.
> > > - Navigating to a new page (or the same page without using null) and
> > > using <redirect/> in your navigation rule.
> > > - Using facelets and not defining the t namespace.
> > >
> >
> >
>
