Re: Why doesn't ActionForm's constructor have access to HttpServletRequest?

I think you really want something other than an ActionForm if you want to do this. Why anyone would use an ActionForm to do this makes no sense to me. If you want the request object, then it is in the Action. That is where it should be. At 06:59 PM 2/2/2004, Martin Cooper wrote: I can't

Re: Why doesn't ActionForm's constructor have access to HttpServletRequest?

Have I missed something here? What is wrong with using the reset method instead of the constructor? That gives you the mapping and the request as parameters. On 02/03/2004 08:17 AM Michael McGrady wrote: I think you really want something other than an ActionForm if you want to do this. Why

Re: Why doesn't ActionForm's constructor have access to HttpServletRequest?

At the moment, I'm in a quandry. I see no way to usefully use nested form beans to encapsulate administrable users in my web app without somehow getting a hold of a list of objects representing those administrable users from the session context of the user who's administering them (the list's

Why doesn't ActionForm's constructor have access to HttpServletRequest?

Is the absence of a reference to the HttpServletRequest object that triggered the creation of a new ActionForm object in its constructor a historical artifact or oversight, or was it an intentional decision whose motivation and rationale remains 100% valid and relevant today? At the moment,

Re: Why doesn't ActionForm's constructor have access to HttpServletRequest?

So... if I implement my own RequestProcessor class that overrides the default processActionForm method to call my own ActionForm-extending bean's constructor an explicitly pass it a reference to the HttpServletRequest object so it can fetch the HttpSession object and find the object that tells

Re: Why doesn't ActionForm's constructor have access to HttpServletRequest?

Not sure how your app is configured, but perhaps you could call an Action to prepopulate your ActionForm, or help it by passing it the request object. --- Jeff Skubick [EMAIL PROTECTED] wrote: Is the absence of a reference to the HttpServletRequest object that triggered the creation of a new

Re: Why doesn't ActionForm's constructor have access to HttpServletRequest?

I can't read Craig's mind ;-) , but I would say that the main reason an ActionForm's constructor doesn't get passed the request (or anything else) is because it is (intended to be) a form *bean*. One of the primary characteristics of a JavaBean is that is that it must have a no-args constructor.