<params> <a1>foo</a1> <b1>bar</b1> ... </params>
and then that would be returned as a single URI parameter. Then it could be parsed as XML and read off really easily, I think. At least, in XSLT, using an EXSL extension function, it would be possible to turn it into usable data to select into.
It's just a theory though. I haven't even tried it yet at all. Do you think it would work?
simon
On Wednesday, October 1, 2003, at 03:49 PM, Vaclav Barta wrote:
Hi,
I have a form producing quite a few parameters (a1, b1, t1, a2, b2, t2 ... a5,
b5, t5), and another page which basically just displays the values from the
first page. This second page uses XSP, and my custom taglib handles each
parameter triple (i.e. a1, b1, t1) by markup like
<eq> <numbers:added> <numbers:num1><param:a1/></numbers:num1> <numbers:num2><param:b1/></numbers:num2> <numbers:sum><param:t1/></numbers:sum> </numbers:added> </eq>
(which is later transformed into a table row). It works, but the same markup
(actually about 3 times longer than the example above) must be repeated 5
times, which is awful. Is there a way to compute the parameter names, IOW can
I specify my markup just once and then call the template with 1, 2 ... 5?
Bye Vasek
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
