Cameron, The components stuff is very cool, but it still has a lot of work to be done as well. As for why the parameter is called "component", that's because both components and objects go through the initialization process. That means that you Action could implement FooAware, which gives Action a Foo object. And Foo could implement BarAware, which in turn gives Foo a Bar object.
-Pat ----- Original Message ----- From: "Cameron Braid" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 05, 2003 9:54 PM Subject: [OS-webwork] XWork ComponentManager - usage of initializeComponent > The ComponentInterceptor, in the before(ActionInvication) method, it > calls initializeComponent(Object) passing the ation. Why is this call > there, shouldn't it be a call to setupComponent(Object) > > I thought the 'operation' of the ComponentManager operations are: > > initializeComponent(Object component) > > store the component so that it can be 'given' to its aware objects > > setupComponent(Object component) > > 'give' any components that are registeded (through > initializeComponent) to the specified component argument. > > Shouldn't the component argument to this method really be named > something different, like object ? > > > > > Cameron Braid > Director > Datacodex Pty Ltd > [EMAIL PROTECTED] > (07) 3844 9199 > (0438) 752 513 > > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
