Issue JAVASERVERFACES_SPEC_PUBLIC-719 asks for something like Apache
Trinidad PageResolver to be added to the JSF 2.2 spec. This issue is
linked to JAVASERVERFACES_SPEC_PUBLIC-809. I'm trying to discover how
best to proceed on these two linked issues and I think the key lies in
re-learning how we use ExternalContext.getResource().
Here are the usages that I have discovered thus far:
Usage1: During RestoreViewPhase when trying to load a page to get its
<f:metadata> section.
Usage2: When trying to render a button whose action uses conditional
navigation.
Usage3: When trying to get the viewId on an initial page request.
Usage4: When trying to serve up a resource request from the filesystem.
Usage5: When trying to find a ScriptComponent Resource for a Composite
Component.
Usage6: When trying to render out the markup for a stylesheet reference
in the HEAD.
There may be others, possibly from the application space as well.
Both 719 and 809 want some kind of API to allow loading resources.
Before proceeding, I want to get people to weigh in to say that the
existing API, decorating the ExternalContext and overriding
getResource(), is not sufficient. Why is it not sufficient?
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/