RE: proposal for bean population

Fair enough as well. It's really minor anyway.

Eelco
  -----Original Message-----
  From: [email protected]
[mailto:[email protected]]On Behalf Of Schnitzer, Jeff
  Sent: donderdag 17 april 2003 23:47
  To: [email protected]
  Subject: RE: [Mav-user] proposal for bean population


  I would rather not make this change in the core - it could lead to a lot
of unexpected behavior, especially if you use a lot of nonmaverick code
(say, third-party filters).  It makes sense to do this in your
application-specific derived controller base class though.



  Jeff Schnitzer

  [email protected]



  -----Original Message-----
  From: Eelco Hillenius [mailto:[email protected]]
  Sent: Saturday, April 12, 2003 3:44 AM
  To: [email protected]
  Subject: [Mav-user] proposal for bean population



  Hi all,



  I propose the following for FormBeanUser, ThrowawayFormBeanUser and
ThrowawayBean:



  Add another populate that get its map from the request attributes. This is
usefull when linking forwards or includes. For example: I use a servlet
filter for jaas based access control. In this filter I set the current
request as a request attribute before using the request dispatcher to
forward to my login command. Using my patch, the bean (be it a form or the
command) is populated, and I can keep on passing this 'saved' last request
between the view and the Maverick command until a login is succesfull
without have to get attributes 'by hand' from the request.



  Find the proposed patches attached.



  Cheers,



  Eelco