Hi Matthias, what do you mean when you say "better way"? The actions are defined by your design and so optimally any actions that are done repeatedly should be coded modularly so you don't repeat the same code in different places.
However your checkLogin might not need to be a whole action - the checkLogin in my current application is a method on a my first action subclass, which has other utility type methods as well. All my real action classes subclass this subclass, and overwrite a performChild() method, which the first subclass class from perform(), after executing checkLogin() Most of my actions end up being two actions - one to process the incoming data, and one to get more data and display it, so I normally have two actions in my flow of control. Adam [EMAIL PROTECTED] wrote: >I Want to que some actions. >For example I've an action checkLogin, an action loadData and an action >display. > >I want that checkLogin gets executed bevore loadData. > >So in the display action in the struts-config.xml >I define a froward "checkLogin" with the path "/checkLogin.do" > >And In the checkLogin I define a forward loadData with the path /loadData.do > >Is there A better way to queue the actions? >Is it better to write the code in just onee action? > >Thanks in advance Matthias. > > >---------------------------------------------------------------------------- >---------------- >Hanel Matthias >Fachinformatiker (Anwendungsentwicklung) in Ausbildung >Logistik World GmbH Fon: +49-841-9014-300 >Marie-Curie-Strasse 6 Fax: +49-841-9014-302 >D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] >---------------------------------------------------------------------------- >---------------- > > >-- >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]>
