Title: Why not let components be declared that aren't used?

We're using Tapestry 2.0.3. A new developer in my group is getting his feet wet in Tapestry and he just came across an annoyance that I recall from my first days with it.

When you declare a component in a .jwc file but don't reference it in the corresponding html template, you get an error when you try to access the page telling you that the component is unused. While this is certainly a good feature in some cases, it can also be annoying.  I understand that on a production system you typically won't want the overhead of unused components but during development when you are trying different things it's nice to be able tinker with the .html and jwc. files independently. As things stand now, you have to go though a complete build/deploy/test cycle before the error will crop up if you've forgotten to comment out a component that you've removed from the html.

Is there some parameter that I'm unaware of which you can use to turn off enforcement of this total mapping between the .html and .jwc files? If not, have others found this to be annoying? We don't use Spindle... perhaps Spindle solves this problem for you??


Reply via email to