On 10/16/06, tm jee <[EMAIL PROTECTED]> wrote:
Hi Ted,
Shouldn't it be
[EMAIL PROTECTED] name="actions.StoryTypeIdList" executeResult="true"/]
or did i miss something.
The name in the Spring configuration is "actions.StoryTypeIdList", but
I believe here we reference the action mapping element name. In the
Struts configuration, that action is then mapped to the Spring bean
(via wildcards).
One issue is validation, so I changed it to
name="StoryTypedIdList_input". In the debugger, I see prepare and
input fire for the enclosing page, and then prepare fire for the
action tag, but not its input method. One would expect both methods to
fire normally.
I copied the code that populates the control to the prepare method,
and I can see that fire too. But, the control is not being populated.
If I add the same data access code to the prepare method for the
enclosing page, the control is populated.
When an action tag is used to execute a result, where are the tags in
the result resolved? One would expect it would be as the result is
being included, so that the markup arrives fully formed in the calling
page. But in this case, we seem to be resolving the tag after it is
included in the enclosing page. Alternatively, one might expect the
action context to be chained back to the calling page, but that
doesn't seem to be happening here.
In the ShowCase, the tree example uses an ActionTag to retrieve a list
of categories. I might try moving that to Spring instantiation to see
what happens.
If anyone is interested, this all pertains to the SportsForge
application, where I'm tinkering with a "Struts on Rails" approach.
* http://opensource.atlassian.com/confluence/oss/display/sportsforge/Home
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
