#113 validate architectural rules

[Ben Eng]

It would be nice to be able to enforce additional
application-level architectural rules that are not strictly
required by Tapestry.

For example, to build jWebUnit testable pages, I would
like to enforce explicit names on @Submit components.

[Geoffrey Longman]

Logged In: YES
user_id=387057

The most I would be willing to do for this is to make a
extension point where another plugin developer could hook
into the build to do this kind of work.

Not something that's going to come anytime soon as the
builder will be changing radically to support the next version
of Tapestry

[Ben Eng]

Logged In: YES
user_id=349359

I agree that it's a very low priority feature. Just wanted to
capture it, while it was fresh in my mind.