In Struts 1.2.4 it slightly simpler...
// do authentication
boolean authentic = authenticate();
if (!authentic) {
getErrors(request).add(logon, new
ActionError(authenticate.error);
return getInputForward();
}
Surely you meant:
new
While I'm at it, other common methods that don't necessarily belong to
Action, but are common enough to be in Struts somewhere: (IMO,
obviously)
getInt(request, attributeName);
// and other common types, Date, Integer, Long ...
Let me add that this method often contains third
While I'm at it, other common methods that don't necessarily belong to
Action, but are common enough to be in Struts somewhere: (IMO,
obviously)
getInt(request, attributeName);
// and other common types, Date, Integer, Long ...
Interesting that Struts lacks probably the first
First I have to say, that I use container managed security for logon -
rather rolling my own with an Action.
Having said that I don't really see what the issue is - just use the same
error mechanism that the validate() method uses - create an
ActionMessages/ActionErrors object, stick the key to
Ah, I didn't know about the saveErrors method. That completely
invalidates my entire concern. Thank you! I figured I was either on to
something or was about to learn something, and I kinda figured it would
be the later :)
Niall Pemberton wrote:
First I have to say, that I use container
On Thu, 30 Sep 2004 20:08:36 -0400, Frank W. Zammetti
[EMAIL PROTECTED] wrote:
Ah, I didn't know about the saveErrors method. That completely
invalidates my entire concern. Thank you! I figured I was either on to
something or was about to learn something, and I kinda figured it would
be the
At 7:01 PM -0400 9/30/04, Frank W. Zammetti wrote:
I came across something yesterday that might be good fodder for a debate...
Another approach which I have used is to consider an authorization
failure a business exception and throw an
UnauthorizedUserException which can then be mapped using
I actually have to plead ignorance on that... In all honesty, I haven't
looked over the sample apps as much as I probably should... I'm one of
those people that prefers to just jump in, start coding something and
figure it out as I go. Plus, I don't generally like looking at other
people's
