Eddy, nothing prevents you from adding a block to the template that
provides you with the name of the exit and use that with
getExitQueryUrl(). You can then include the common list template and
have the exit name in the including template, if that's where you
want that to be located.
On 2-mrt-06, at 17:03, Eddy Young wrote:
Geert Bevin wrote:
Hmmm, well you can instead of using 'EXIT:QUERY:exitname' as you
value tag, use 'myexiturl'. Then in one element you set the value
with what you obtain from getExitQueryUrl (using that element's
exit) and in the other element you do the same but with the other
exit. Wouldn't that work?
It would, but I wanted to avoid passing the exit to the populateList
() method -- PersonTemplateHelper should know about the exits
specified in the template.
Given that the name of the exit is specified in the EXIT:QUERY tag,
it would great if something like template.setExitOutputs(String
exit, String[] outputs) could take care of setting the query string.
Now, if I wanted to use an embedded element, how would you suggest
I go along doing this?
Eddy
--
http://coding.mu
http://priscimon.com/blog
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
