HstComponents of type hst:containercomponent should be able to have default builtin template

If we have for example the following hst:containercomponent with the following property:

hst:containertype = table

This means, that we 'know', the renderer should be some table.jsp

However, we cannot package jsp files in a jar. As these jsp's are so simple, we could also write them as packaged java classes (or use freemarker template).

Thus, for a hst:containercomponent that does not have a template, we have to know two things:

1) The server side renderer (for example org/hippoecm/hst/pagecomposer/TableRenderer.java)
2) The client side renderer (for example Hippo.DD.Container.Table)

We could easily add this mapping in some Spring component. But, what would be the cleanest way to include the following behavior into the HST:

1) When in composermode, we should add wrapper elements containing an attribute hst:containerType = 'Hippo.DD.Container.Table' . Currently temporarily added to the aggregation valve
2) In the invokeRender from HstComponentInvokerImpl, we do not have a dispatch URL but execute some java class or built in freemarker template?

WDOT?