> -----Original Message----- > From: Travis Chase [mailto:[EMAIL PROTECTED]] > Ok last question I promise. I have been going through the > code and I see where almost everything is being done. The > only thing I still am having trouble with is if the Digester > loads the ActionMapping objects and the RequestProcessor > loads the Action objects, how does the Action object get at > the dynamic properties set in the set-property element of the > action element? I would think either the ActionMapping > object would have to have a collection of the properties for > the Action to query or someone would have to set the > properties on the extended Action object. Is this correct? > Where am I missing the tie between? Thank you for being > patient and answering my questions. Great framework!
The <action> element in struts-config.xml actually represents an ActionMapping object, in a rather confusing turn of events. So the ActionMapping instance is the one that can have properties set on it. Action instances do not exist when the Digester plows through struts-config.xml. A "property" in this case is basically a Javabean property. So if you do a set-property of "name", then if your ActionMapping subclass has a public void setName(String) method on it, it will be called. Hope this helps, Laird -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
