The original issue was that that page fragments that were included for each component that generated the IFrames for the Description and Source tabs used relative references to retrieve their content: For example:

<iframe src="./docs/selectInputTextDoc.html"
               class="includeIframe"
               width="100%">
</iframe>

This did not work in portlets, so the original fix was to hard code the context to the path to make it absolute. Like this:

<iframe src="/component-showcase/docs/selectInputTextDoc.html"
               class="includeIframe"
               width="100%">
</iframe>

Unfortunately, this makes things a bit fragile. If the .war file isn't named exactly right (i.e. component-showcase.war), then the context is incorrect and the IFrame content can't be found. This showed up prominently in Jetspeed 2 were the deployment process requires that the deployed war is prefixed with the term "jetspeed" (i.e jetspeedcomponent-showcase.war).

So we need a way to dynamically include the context in the src path in a way that works for both portlets and web-apps.