I use a collection of maps all the time for both form input and grid output. I have a report system that stores sql in the database and uses a beaneditform for query parameters and a grid to display the result set. It's turned out to be extremely useful. I use a PropertyConduit just like you suggested but with one addition. Instead of using Object.class I created MapData.class All it does is provide get, put and getMap methods, but this allows Tapestry to auto construct the object. For a grid this does not matter but it's very useful when using it with beaneditform.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
