See below: > -----Original Message----- > From: Michal Mosiewicz [mailto:[EMAIL PROTECTED] > Sent: Monday, September 01, 2003 8:22 AM > To: opensymphony-webwork > Subject: [OS-webwork] ActionInvocation.invoke() multiplicity > and various thoughts and questions > > > Are there any whitepapers on xwork beyond wiki? > Nope.
> I can't resolve the following issue - is this assumed that > invoke() may only be called once per instance, or multiple > times (I mean single request)? > Invoke on ActionInvocation? It is executed multiple times. Each call moves it forward in the Interceptor chain, so each Interceptor calls this to allow the rest of the processing to occur. Execute() on ActionProxy can only be executed once, I think. > Continuing my previous letter - now I see there is really no > assumption that actions may be used to create view > _components_. I can only see there is an UI-Component notion > that is limited to calling velocity template. I see my > mistake in how I percepted what ww:action tag is designed > for. I thought that it could be used for view > componentisation, but it can only serve as an action oriented > jsp:useBean replacement. > See the Jira issue I created for creating an ActionComponentTag which will both execute an Action and include its view. This should allow for view components. > To accomplish my ideas on using xwork's value stack, I took > my chance with jsp:include to dispatch to another action with > patched DispatchServlet to build up on existing stack (to > accomplish single stack per request, not per > action) instead of creating one. That would even work - but > there is another issue - it seems that it is assumed there is > no action nesting. When ActionInvocation pushes Action onto > the value stack, it never takes it away - so in case of > nested calls the stack would build-up endlessly. Actions can be nested, for instance if you look at ActionChainResult, but it is done only in specific carefully controlled spots. Rather than clean up the ValueStack by popping, we just clean up the whole ActionContext. > > I would probably be interested to patch things up to > accomplish action nesting, but the problem is that there are > probably things I'm not aware. Specifically if invokes are > single or multiple. Personally I think that assumption that > invocation is once per instance would be easiest. However > I've got some interesting cases that having interceptor > invoking action multiple times would be nice - for example it > allows to reuse the action designed to work with a single > object and to call it over a group of objects simply by > changing properties and calling again (setting properties on > multiple object, deleting objects, etc). > Let me know if what I've proposed meets your needs. > Regards, > -- Mike Mosiewicz > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
