Forgive me for replying to myself, but I think I may have figured out
what's going on: the second bean is not populated from the first bean
as I mistakenly assumed -- it's populated from the request! So, just as
the first bean got its name from the request parameter, the second get
its name from there, too.
Jim Crossley wrote:
>
> I think I found a bug or, as Larry Wall might say, it would be difficult
> to interpret it as a feature. :-)
>
> I have an Action that occasionally needs to forward its request to
> another Action. So the <forward> element in its corresponding <action>
> element has a path with a suffix of "do" instead of "jsp". The
> associated form bean classes for each action's form have a "name"
> property, though this is purely coincidental. They have no real
> relationship.
>
> Oddly enough, when Action X forwards to Action Y, the name property for
> Y's form bean is initialized to the name from X's form bean! Is this a
> bug?
>
> Thanks.
