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!
-Travis -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 7:57 PM To: Struts Developers List Subject: RE: Action question On Mon, 27 Jan 2003, Travis Chase wrote: > Date: Mon, 27 Jan 2003 16:10:11 -0600 > From: Travis Chase <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Subject: RE: Action question > > Great I see where that code is happening, so my next question is if the > Digester loads all the actions what is the purpose of having the > RequestProcessor do the same thing? > Digester does *not* load the Action classes themselves, it only instantiates the ActionMapping instances. An Action instance is not created until the first time you ask for it. Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
