|
From: Steven D. <ste...@gm...> - 2005-08-06 14:55:11
|
Hi, I noticed the parent request scope is empty when a sub flow terminates. Why is this, it makes sense to keep it. If I want to select an entity from a form I submit the entire for to a form action. Next I start a sub flow to do the selection and the output part of the flow attribute mapper gets the command object from the request and binds the selected entity to the command object. But since the request is empty after the sub flow completion I have to put the form action in flow scope and put the command object in the request scope myself after the sub flow completes so that the form view in the parent flow renders propertly. Keeping the request scope intact would be easier. Please advise Steven=20 --=20 "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart |