See below: > -----Original Message----- > From: Michal Mosiewicz [mailto:[EMAIL PROTECTED] > Sent: Monday, September 01, 2003 5:11 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Why is that... > > > I'm just taking my hands on webwork/xwork. Very nice, cool > and simple solutions comparing to what I used to work with > (like struts). > > But still the more I'm getting inside, I discover many things > not working as I would estimate it would work. > > Notably there is one thing that I thought it must be a bug in > the servlet dispatcher, that it doesn't preserve value stack > for included requests. Then I also discovered that this > pattern is repeated in other places, like ActionTag. >
ActionTag just executes an Action and makes it available for the rest of the page by binding it into the PageContext and ActionContext with the supplied id. > I would rather expect that there is only one stack per > request, and during the processing of the request this stack > is built up and poped. You can push anything onto the stack using the push tag. > > Specifically there are patterns I wanted to move from my old > code (built up upon struts) that were very useful. For > example I would like to do something > like: > > <ww:iterate ...> > > <ww:action name="ClassBasedDispatcher" ... /> > > </ww:iterate> > > where the action above includes different viewes depending on > the object's class being currently iterated. > > That way I can reuse the same base 'container view' and > attach different 'element views' automatically. > > Previously I implemented it only using tags, but as you may > guess - to implement this I had to introduce something like > xwork's value stack. Then - when I spotted xwork/webwork I > thought that the solution here is very similiar. > > But now it seems that value stack only works for single > action, and it doesn't build up for nested actions. So why is > that? I noticed that ActionTag even contains code to link the > stacks, but it's carefully commented out. This is because the ActionTag only allows included param tags inside, not actual templates, therefore it's not necessary to push it onto the ValueStack. You can manually push it onto the ValueStack using the push tag immediately afterward. I think what you're asking for is a cross between the ActionTag and the ComponentTag. Basically, you want to execute an Action and include its template. I think I like this idea, even though it has some potentially dangerous side-effects. We'll have to be careful about dealing with the output streams, etc... I'll create a Jira issue for this: http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-286 > > Second question - which CVS is currently in use, and where > should I send issues, patches, etc? I'm new here... > We're using the CVS on dev.java.net: https://webwork.dev.java.net/servlets/ProjectSource Issues, etc are handled at http://jira.opensymphony.com Docs are at http://wiki.opensymphony.com > Regards, > -- Mike > > > > > ------------------------------------------------------- > 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
