Right.   We know the navigation rules are correct which is why I
didn't ask for them.  The jsp code and possibly the managed bean
definitions are what we need to see.

On 1/17/06, Garner, Shawn <[EMAIL PROTECTED]> wrote:
> <navigation-rule>
>     <from-view-id>/context07/summary.jsp</from-view-id>
>     <navigation-case>
>       <from-outcome>college</from-outcome>
>       <to-view-id>/context07/college.jsp</to-view-id>
>     </navigation-case>
>
>     ... rest of navigation-cases
> </navigation-rule>
>
> if I type in /context07/college.faces in the url the college page comes
> right up.
>
> However the <h:commandLink action="college"/> on the summary page I have to
> click on it and then click on it again.
>
> Shawn
>
> -----Original Message-----
> From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 17, 2006 2:39 PM
> To: MyFaces Discussion
> Subject: Re: another commandLink problem
>
> Can you post your jsp or facelets page code?
> It's not really possible to give anything beyond the vague answers
> below without more specific information.
>
> It'd probably also be helpful to post the faces-config information for
> any managed beans being used.
>
> On 1/17/06, Garner, Shawn <[EMAIL PROTECTED]> wrote:
> > I don't get what the problem is then?
> >
> > Shawn
> >
> > -----Original Message-----
> > From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 17, 2006 2:27 PM
> > To: MyFaces Discussion
> > Subject: Re: another commandLink problem
> >
> > Right, but the second time you've clicked on the link, the page has
> > been redrawn, the component tree updated, and the request map reset,
> > etc, so that doesn't really eliminate any possibilities.  :)
> >
> > If you're using a hardcoded action literal string, then yes, you can
> > eliminate the navigation manager cause.   If you're not using rendered
> > in the link or any of its ancestors, you can eliminate that.   If
> > there's a UIData component in the ancestors, that's the likely cause
> > -- you need to preserve the backing data model between requests.
> >
> > On 1/17/06, Garner, Shawn <[EMAIL PROTECTED]> wrote:
> > > Well I'd say it's definitely know to the navigation handler because it
> > finds
> > > the page the second time I click on the same link.
> > >
> > > Shawn
> > >
> > > -----Original Message-----
> > > From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, January 17, 2006 2:14 PM
> > > To: MyFaces Discussion
> > > Subject: Re: another commandLink problem
> > >
> > > If the returned string for the action is null or unknown to the
> > > navigation manager, it'll show the same page again.
> > >
> > > Also, if the commandLink isn't rendered either before or after the
> > > request, it'll return the same page.  Same thing if the link is inside
> > > a UIData component and the UIData model isn't preserved across
> > > requests (t:saveState on request-scoped data).
> > >
> > > On 1/17/06, Garner, Shawn <[EMAIL PROTECTED]> wrote:
> > > >
> > > >
> > > >
> > > > I've noticed my commandLinks don't go to the page the first time.  It
> > > seems
> > > > to reload the page and then if I click on it again it goes to the next
> > > view.
> > > >
> > > > Anyone know what is causing this, how to fix it?
> > > >
> > > >
> > > >
> > > > Shawn
> > > >
> > > >
> > >
> >
> ****************************************************************************
> > > >
> > > > This email may contain confidential
> > > > material. If you were not an intended recipient,
> > > > Please notify the sender and delete all copies.
> > > > We may monitor email to and from our network.
> > > >
> > > >
> > >
> >
> ***************************************************************************
> > > >
> > >
> > >
> >
> ****************************************************************************
> > > This email may contain confidential material.
> > > If you were not an intended recipient,
> > > Please notify the sender and delete all copies.
> > > We may monitor email to and from our network.
> > >
> >
> ****************************************************************************
> > >
> >
> >
> ****************************************************************************
> > This email may contain confidential material.
> > If you were not an intended recipient,
> > Please notify the sender and delete all copies.
> > We may monitor email to and from our network.
> >
> ****************************************************************************
> >
>
> ****************************************************************************
> This email may contain confidential material.
> If you were not an intended recipient,
> Please notify the sender and delete all copies.
> We may monitor email to and from our network.
> ****************************************************************************
>

Reply via email to