> wouldn't adding methods to the existing interfaces lead to libraries written for (and compiled against) Tapestry 5.3 would not work with Tapestry 5.4 anymore?
In this instance, I would assume an AbstractMethodError would be thrown when calling the new method: ComponentResources.getBoundGenericType(paramName) This would only occur in third party bindings / propertyConduits that don't extend core (internal) implementations. IMHO these exceptions are likely to be rare as hen's teeth ;)
