hst:ismapped behaviour on a hst:mount is not implemented correctly as it next to sitemap mapping true or false it now also assume content mapping true or false

We only need to change its behaviour to what I think everybody thinks it is. (I think it is currently a bit broken, probably implemented incorrectly by me like one year ago).

I think the behaviour must be (very simple):

hst:ismapped = false : no sitemap matching
hst:ismapped = true : with sitemap matching

Right?

Currently, it has some extra behaviour, namely: When 'false' , the HST does assume the hst:mountpoint is to a canonical real content location and never to a hst:site containing a mirror. This results in, that when you have hst:ismapped = false, and still have a mountpoint to a hst:site , that searches never work: The HST then searches in the facetselect node, but does not re-map that to a canonical content search.

If you both agree with that the current implementation is actual broken (I did not do it correctly before), then I'll create an issue to fix that. It is only softly related to the ./ thing, but I was in the mindset that due to this, even a plain jaxrs pipeline always uses sitemap mapping, hence, also, I suggested the ./
But instead, I perhaps should have solved this issue instead. What do you think? Hope it is also more clear where my reasoning came from regarding ./