> -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > > In a different message, David wrote: > > It would really be useful if you could step through this in the debugger > and try to see > > what's happening, starting at the (expected) call to the attribute > setter > in the form tag > > up to that line in RequestUtils where the "action" parameter is > apparently > null. > > What do you mean by "action" parameter? I use "action" to control a > LookupDispatchAction, but this one (ChooseProfileAction) is a plain old > Action.
I'm referring to the method which is throwing the exception, which is "RequestUtils.getActionMappingName()". Line 577 is a reference to the "action" parameter, and is the only likely source of an NPE on that line. If you were to trace the execution path in your debugger, you should be able to verify that it is the "action" parameter that is null, and tracing from the setter calls on the tag up to here should give you a clue why it is null. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
