Sending a command to be executed is classic strategy / command pattern. It's good because it allows you to send the object you want to be run pre-populated... > -----Original Message----- > From: Brock Bulger [mailto:[EMAIL PROTECTED] > Sent: Friday, July 11, 2003 12:35 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Xwork IoC requirements > > > I was reading you comments on the pico issue and thought that > this was a strange use case. Why would you define an Action > used by your swing app with component dependencies that had > to be set in the ClientDispatcherServlet? I would think you > would just proxy your data or model to a custom > ClientDispatcher that would create the Action and resolve the > dependencies. Then your model/data is the only part that has > to be serialized (and not the whole Action). > > > ----- Original Message ----- > From: "Jason Carreira" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, July 11, 2003 11:21 AM > Subject: RE: [OS-webwork] Xwork IoC requirements > > > I'm not talking about the container. I'm talking about an Action. > > Lets say I create an Action in a Swing app and populate it > with some data. Then I send it, serialized, to a special > ClientDispatcherServlet which deserializes the Action and > executes it.... Except it has component dependencies... The > services it depends on can't be available in the Swing app, > so it needs to re-wire them on the server before executing it. > > Jason > > > -----Original Message----- > > From: BOGAERT Mathias [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 11, 2003 11:28 AM > > To: '[EMAIL PROTECTED]' > > Subject: RE: [OS-webwork] Xwork IoC requirements > > > > > > On another note: > > > > Jason, what the f*ck are you talking about?? Can you > explain the issue > > with requirement 3? If the container can be serialized, and the > > components too, what is the issue then? Why do you need to re-wire > > after serialization/deserialization? > > > > Cheers, > > Mathias > > > > -----Original Message----- > > From: Jason Carreira [mailto:[EMAIL PROTECTED] > > Sent: vrijdag 11 juli 2003 16:24 > > To: [EMAIL PROTECTED] > > Subject: [OS-webwork] Xwork IoC requirements > > > > > > I'm starting a list of requirements for an IoC container in Xwork. > > Here's what I've got so far: > > > > 1) Ability to have nested component scopes (Application -> HTTP > > Session > > -> HTTP Request -> Action Invocation) > > 2) Ability to resolve component dependencies and create components > > with dependencies fulfilled > > 3) Ability to re-wire component dependencies separate from > > construction > > -> needed to re-wire components after serialization / > deserialization > > > > Picocontainer can not and will not (as far as I can discern > from the > > mailing > > list) support requirement 3, so I suggest we remove > Picocontainer and > > restore the previous IoC code for now, while we examine other > > alternatives, such as Spring. > > > > Jason > > -- > > Jason Carreira > > Technical Architect, Notiva Corp. > > phone: 585.240.2793 > > fax: 585.272.8118 > > email: [EMAIL PROTECTED] > > --- > > Notiva - optimizing trade relationships (tm) > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by: Parasoft > > Error proof Web apps, automate testing & more. > > Download & eval WebKing and get a free book. > > www.parasoft.com/bulletproofapps1 > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by: Parasoft > > Error proof Web apps, automate testing & more. > > Download & eval WebKing and get a free book. > > www.parasoft.com/bulletproofapps1 > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book. > www.parasoft.com/bulletproofapps1 > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book. > www.parasoft.com/bulletproofapps1 > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
