Sounds cool. I like the idea of a Ant taskdef to validate this. I hope to look over the code this weekend-ish (I'm working part of the weekend). I don't see a reason why this could not be rolled into the framework proper.
I've done this sometimes using the Inspector to force pages to be loaded, but this is better and faster. I think Tapestry should do a little more validation as it reads specifications ... it needs more things like checks for duplicate binding names or parameter names, etc. -- [EMAIL PROTECTED] http://tapestry.sf.net _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
