Since I always seem to be asking questions and receiving help, I thought I
would let you know how I finally solved this problem.
What was wrong was in the naming of my jsps (the view-ids). I changed my
faces-config.xml from:
loggedOff
/failure.jsp
to
loggedOff
[EMAIL PROTECTED] wrote on 10/14/2005 02:51:05 PM:
> On 10/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > 3. Next I click on logoff and this is where stuff gets goofy.
> > Logoff link points to "logon.logoff". LogActions.logoff() does some
stuff
> > and then returns "unauthenticated"
Wendy Smoak <[EMAIL PROTECTED]> wrote on 10/14/2005 03:27:30 PM:
> From: <[EMAIL PROTECTED]>
>
> > Wendy, I am currently using eclipse's built-in debugger to step into
the
> > code. Would you recommend something else?
>
> No... your original message sounded like you were just looking at the
lo
From: <[EMAIL PROTECTED]>
Wendy, I am currently using eclipse's built-in debugger to step into the
code. Would you recommend something else?
No... your original message sounded like you were just looking at the log
file output. Right after I sent that, you posted about setting breakpoints.
Wendy Smoak <[EMAIL PROTECTED]> wrote on 10/14/2005 03:12:36 PM:
> From: <[EMAIL PROTECTED]>
>
> >I have been trying all day to understand exactly where and when Shale
> > injects into the JSF life cycle and I think i'm almost there..:)
>
> By looking at the log files? Have you stepped through
From: <[EMAIL PROTECTED]>
I have been trying all day to understand exactly where and when Shale
injects into the JSF life cycle and I think i'm almost there..:)
By looking at the log files? Have you stepped through the code in a
debugger? After you get past the initial setup, it will save y
[EMAIL PROTECTED] wrote on 10/14/2005 02:58:10 PM:
> On 10/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > "David G. Friedman" <[EMAIL PROTECTED]> wrote on 10/14/2005
02:51:13
> > PM:
> >
> > > If you are doing a logout, wouldn't it be quicker to do an
> > immediate="true"
> > > along
[EMAIL PROTECTED] wrote on 10/14/2005 02:51:05 PM:
> >
>
> The implication of this sequence of events is that the navigation
requested
> by "unauthenticated" did not actually happen, so it's redisplaying the
same
> page again. Are you sure you've got the navigation rules set up
correctly,
> so
On 10/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> "David G. Friedman" <[EMAIL PROTECTED]> wrote on 10/14/2005 02:51:13
> PM:
>
> > If you are doing a logout, wouldn't it be quicker to do an
> immediate="true"
> > along with your action invocation? Then you could skip the other
> phases.
"David G. Friedman" <[EMAIL PROTECTED]> wrote on 10/14/2005 02:51:13
PM:
> If you are doing a logout, wouldn't it be quicker to do an
immediate="true"
> along with your action invocation? Then you could skip the other
phases.
> It is in your logout/logoff after all, right?
Oh, I guess that is
On 10/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> 3. Next I click on logoff and this is where stuff gets goofy.
> Logoff link points to "logon.logoff". LogActions.logoff() does some stuff
> and then returns "unauthenticated" which is mapped in faces-config.xml to
> /failure.jsp which in
[mailto:[EMAIL PROTECTED]
Sent: Friday, October 14, 2005 2:29 PM
To: user@struts.apache.org
Subject: [Shale] Help - wonky prerender() call!
I have been trying all day to understand exactly where and when Shale
injects into the JSF life cycle and I think i'm almost there..:) But I do
have one
I have been trying all day to understand exactly where and when Shale
injects into the JSF life cycle and I think i'm almost there..:) But I do
have one question which reads rather long, so please bear with me.
Here's what I do with my Tiles+Shale webapp:
1. Acces it via: http://www.myContext/
13 matches
Mail list logo
