On Wed, 2009-03-11 at 11:05 -0700, Frank Hamilton wrote: > I need to load some select in cascade. > > Example: > > A: Colors --> if select Colors then --> B: Blue > Number > > Red > . > > Cian > . > > When I execute my initParameter() in the usecase handler (extend > AbstractUsecase), I load the A options, and the B options is empty. I > setParameter(lstA) and get in jx file. > > When change the select with the A options I need to set the options in > select attribute. I prefer not use ajax for this. > > Now I use this in jx: > ... > <select name="idA" id="A" > onchange="location.href='?idA='+this.value" > > .... > > Then I start the usecase again,and in the initParameter() get the request > parameter idA execute my method getAtributeByA(getParameter(idA)). Then I > sent the list of attribute and fill up the B select in jx. > > But need to set again A list, or save this in session In the first execute > of usecase to get it in the second execute or usecase. > > How can I use a workflow of usecase form keep attributes in usecase. > > Can somebody see me an example for this.
As I understand Frank, his problem is that he needs a multiple step usecase and he does not know how to do it. His example is comparable with the typical car flow example of cocoon, where you select one thing and the next select box depends on that. It would be fairly easy to implement this with custom flow however I am unsure myself how to do this multiple step flow with our usecase framework. If somebody has an suggestion or experience how to implement this it would be wonderful to share it. TIA salu2 -- Thorsten Scherler <thorsten.at.apache.org> Open Source <consulting, training and solutions> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
