struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Struts Wiki] Update of "RoughSpots" by GabrielZimmerman
Date Wed, 19 Apr 2006 18:31:52 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.

The following page has been changed by GabrielZimmerman:

      * [jcarreira] I'm not sure that's useful... We discussed it at some length on the mailing
list and it wasn't clear. mapping the param interceptor twice isn't for that problem, though,
it's for model-driven actions.
      * [crazybob] I'm not sure what you discussed, but it's *very* useful, and there should
be no reason not to do it. Say for example my form has a 'userId' and fields to set on the
user '', 'user.address'. With the sorting, 'userId' gets set first at which point
we load a `User` object. Then the other parameters get mapped to that `User` object. Without
the sorting, there's no guarantee on the ordering. You have to load the user in one action
and then chain to another. This is a common use case; might as well make it simple.
+     * [Gabe] Discussion here: []
Basically, I think we can come up with a better way to accomplish this than requiring setter
methods to be used for business logic and depending on parameter ordering.
  == Nice to haves ==

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message