Support multiple component configuration mappings PER sitemap item

Currently we cannot easily support a single sitemap item to render completely different component hierarchies. This is because there is only a single hst component configuration id PER sitemap item.

Also, this makes it really hard to have folders that contain mixed document types, say agenda and news items.

What we'd like to be able to support is the following:

Sitemap item

**.html

• hst:componentconfigurationid = hst:pages/detailpage
• hst:componentconfigurationidMappings = {myns:newsdocument = hst:pages/newspage, myns:agendadocument = hst:pages/agendapage}
• hst:relativecontentpath = common/${1}

Now, if the relative contentpath points to a document of type newsdocument, the page will be rendered as a hst:pages/newspage, if it is a agendadocument it will be rendered as a hst:pages/agendapage and otherwise as the default hst:pages/detailpage

This makes it also possible to store any documenttype directly in, say the folder 'common' and render it completely differently.

Note: because jcr does not support a map of course, we use

• hst:componentconfigurationmappingnames (string) multiple
• hst:componentconfigurationmappingvalues (string) multiple

similar to parameternames and values