On Wed, 2002-03-13 at 22:41, Kurt Schrader wrote: > > On Thu, 14 Mar 2002, Scott Eade wrote: > > > At the end of a doPerform() method I want to trigger a separate action. Can > > I just do this?: > > > > OtherAction oa = new OtherAction(); > > oa.doPerform(data, context); > > That will work. It's probably just better to to not have much logic in > your actions though. I just get the parameters I need and pass them to > the objects that need them to run. That way you can use the same logic in > any number of actions.
+1 If you are going to use actions and place logic in there that manipulates your object model then make them execution environment agnostic. By that I mean remove the dependency on the servlet in your actions. This will be part of the roadmap for 3.0. Where the core of your turbine app is contained in an application model and there will be different conduits to bring information from the view to the model. As Kurt pointed out all you really need is a mechanism to get the values need by your 'action' to perform it's job. The 'action' shouldn't care where those values come from. Currently in Turbine it is usually from a web page, but we certainly don't have to limit ourselves to this. > -Kurt > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
