Re: [Keelgroup][ANN] Navigate and dynamic parameters

Well, setting request attributes is the same issue.  The subsequent 
models in a Sequence only return a response, and can't modify the 
request. (they can modify, but it doesn't get passed on, unless I've 
done something wrong)

So, my next option, which is probably the cleanest, as far as keeping 
models independent of each other, is client code, jstl, that will parse 
and replace.  That way, you don't have to *know* before submitting what 
your variables will be on the next view, because as it is now, it only 
works with submitted request parameters.

I guess its time to learn a little more jstl.

thanks,
gene

Gene McCullough wrote:
> Correct, using Sequences, the responses are merged in the "controlling" 
> sequence model based on configuration, and not available to individual 
> models in the sequence.  I'll test out the request attributes and report 
> back.  I had that thought, or also maybe adding a request parameter.
> 
> Either way, it will require some kind of project coding standard, as to 
> where or when to add the parameter or attribute, so that it can be found 
> when expected.
> 
> This all assumes you're using Sequences.  If you're "chaining" the 
> models by calling them from other models, the Outputs *are* available.
> 
> Does app-workflow handle this any differently?
> 
> thanks
> gene
> 
> Sasvata (Shash) Chatterjee wrote:
> 
>> Gene,
>>
>>> Hmmm, I was a little premature on stating this uses Outputs in the 
>>> response.  It DOES work with request parameters, but NOT with 
>>> Outputs. I was assuming, using the Sequence model, that responses got 
>>> merged and passed along to the individual models.  That is not the 
>>> case.  I'm not sure how app-workflow handles this.
>>
>>
>>
>> Responses (and Outputs) *should* get merged by default, but the 
>> intermediate models don't see that (they are not supposed to be aware, 
>> or assume, that other models have gone through in any particular 
>> order).   The Sequence itself keeps a running merged response which is 
>> returned back to the client.  If I remember correctly, you can try 
>> adding the outputs as a *request* attribute, that just might work.
>>
>> Shash
>>
>> http://keelframework.org/documentation.shtml
>> Keelgroup mailing list
>> [email protected]
>> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
> 
http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com