I would say the Tapestry way to override persist behavior is with Meta and it should probably stay that way. Secondly I'd prefer making the default the preferred way and overriding that behavior instead of the other way around.
The thing Tapestry does not provide out of the box is override Persist by type which is what I think you need in this case. I would think persisting the grids String, Integer and Boolean in the url would be a good idea. Finally I think it would work in the url even with multiple components on the same page. You just need to differentiate them somehow. In my paging component I use the component id/field name. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Does-the-Tree-component-need-to-use-the-session-tp5667428p5670613.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
