[orbeon-user] The resource retriever portal style --- parameters

[stephan]

>  > Hhm once we touch resource-managers could we come up with a portal
>  > compliant resource manager? I analyzed IBM portal and what they do
>  > is actually clever.  They retrieve a) the browser b) the language c)
>  > the theme (via cookie) and search for the most specific
>  > resource. (They do it in JSP only <find-in-resource id="logo.gif"
>  > />). SO it searches for /resources/spring/moz7/en/logo.gif then
>  > /resources/spring/moz7/logo.gif then /resources/spring/logo.gif then
>  > /resources/logo.gif. The first match is retrieved and cached....
>  > This way broser specifics (mostly _javascript_ and CSS) and Themes
>  > could be implemented with a blink.
>
> My only worry would be to consider how such a mechanism could be made
> generic. Retrieving the resource depends on certain parameters, but
> which ones? Do you hardcode the fact that it looks for the browser and
> the language?
>
> -Erik
I will dig out the calling sequence. I'm not sure if that is the portal standard. I modeled the function after the behavior of an JSP Tag in IBM Portal4. So at least it would be compliant with their directory structure. We could configure the sequence if other portals do it differently.