Hi Ralf,
Ralf Fischer-2 wrote: > > Please tell us exactly what you want to do, as there might be a > simpler solution to your problem. > Okay I don't have hibernate and this is what I'm sort of doing. Let's say that I have a table of staffs, offices and things_assignment (which links staffs and stuff to offices and whatever). I'm displaying rows of staffs with the office they are assigned to. There are many solution to this... I mean I can write an sql to grab the property as well as the staff and dump them in a Staff object that has property object inside it (and whatever else that can be assigned to a staff), that would make sense I just want to keep things separate. Ralf Fischer-2 wrote: > > As your workaround seems to be to "invoke back" actionA from your > example, I guess there's another result for actionA which then renders > the data which results from actionB into the page. > This can either be > done using the action chaining (which seems to be discouraged as I've > learned from this maling list) where you don't have to invoke the > action from the JSP but as a result directly, or simply render the > data inside the action tag, doing something like this: > | <s:action namespace="/foo" name="bar" executeResult="false"> > | <s:property value="myPropertyFromTheBarActionImplementation" /> > | </s:action> > Yes actionA finds record A from a field in record B which is fetch from actionB, and actionA displays the 'name' attribute from a. ActionA from actionB was only called once so there's no 'invoke back'. So the intention originally was actionB renders nothing but redirect to actionA which renders something, which works when called directly to actionB but when actionB is called from part of a JSP (say when I'm rendering rows of objects C and want to display object A's name in one of the column, which is associated to C via object B's CId [b.id I mentioned before was meant to be b.CId] and blahId), but when I actually try that it doesn't move to actionA after performing actionB. I was looking at action chaining and the page say to use 'redirect' or 'redirectAction' instead which is the approach I chose but it didn't do what I thought it would. Hope I'm making sense here... Anyhow the workaround works I'm more just curious as to why redirect-action doesn't work in this instance. I mean surely not all <s:action with executeResult set to true would render a separate HTTP header.... right? ... or do they? Thanks, CC -- View this message in context: http://www.nabble.com/jsp-page-with-s%3Aaction-to-call-an-action-with-a-redirect-action-tp16951812p16973314.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
