In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
> As long as you have users that have passwords, and that might be in zero or
> more roles, it should be relatively easy to write a realm implementation
> that would access your custom user information repository. That would allow
> you to
"Craig Edwards" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] says...
> > You could do that... or you could do it the J2EE way, decleratively
> > without any coding, letting container do it that way:
>
> Thanks for the reply Vic.
On 11/17/2003 12:11:37 PM Adam Hardy wrote:
> Sorry, I meant post
For this application, the user must be logged in before hitting any pages,
so I needed to only cover cases for when the user types in a URL from
outside the application. I didn't give that a thought, so I perhaps this
isn't too he
Sorry, I meant post
On 11/17/2003 05:58 PM Kris Schneider wrote:
Just a note that ActionServlet only implements doGet and doPost so I imagine
you'll get some sort of method-not-supported error (inherited from HttpServlet)
if you send it a PUT request.
Quoting Adam Hardy <[EMAIL PROTECTED]>:
Susan,
Just a note that ActionServlet only implements doGet and doPost so I imagine
you'll get some sort of method-not-supported error (inherited from HttpServlet)
if you send it a PUT request.
Quoting Adam Hardy <[EMAIL PROTECTED]>:
> On 11/17/2003 02:31 PM Susan Bradeen wrote:
> > I have been using th
On 11/17/2003 02:31 PM Susan Bradeen wrote:
I have been using the following for returning the user to their intended
URL after a login, and have had good luck with it ...
- In the Base Action class -
if (someCheckFor.loggedInUser() == null) {
StringBuffer goToPath = new StringBuffer(reque
I have been using the following for returning the user to their intended
URL after a login, and have had good luck with it ...
- In the Base Action class -
if (someCheckFor.loggedInUser() == null) {
StringBuffer goToPath = new StringBuffer(request.getServletPath());
if (request.getQue
On 11/17/2003 05:29 AM Craig Edwards wrote:
To complete process X, the user has to perform 5 steps. The user can
perform steps 1, 2 and 3 with or without being logged on, but they must
be logged on to perform steps 4 and 5. Obviously, I can have a specific
check in step 4, but I would like, sa
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] says...
> This might be more involved than you may think. The easy answer is to extend
> the RequestProcessor and add this functionality there. The hard answer is
> that you may not want to enable a user to just jump to any given page, only
> havin
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] says...
> You could do that... or you could do it the J2EE way, decleratively
> without any coding, letting container do it that way:
Thanks for the reply Vic. I can see how that would be the way to go if
I were starting from scratch. Unfortun
such). And yes I think this should on some level be
part of Struts. It's too common for it not to be ...
just my .02
Rob
-Original Message-
From: Craig Edwards [mailto:[EMAIL PROTECTED]
Sent: November 14, 2003 10:12 PM
To: [EMAIL PROTECTED]
Subject: Redirecting after logon...
Some
L PROTECTED]
> Sent: November 14, 2003 10:12 PM
> To: [EMAIL PROTECTED]
> Subject: Redirecting after logon...
>
>
> Some of my pages need the user to be logged on before they can be
> viewed, so I have cobbled together some simple behaviour in my Action
> superclass that forwards
Some of my pages need the user to be logged on before they can be
viewed, so I have cobbled together some simple behaviour in my Action
superclass that forwards them to a logon page. Now, I need to send them
back to where they were originally trying to go before I redirected them
to logon. I
13 matches
Mail list logo
