Hi EG,
I think we nearly have it, with a little limitation to prefix-mapped resources and non versioned resources.
If the ResourceHandler would always generate urls without the question mark, one could use the usual references with ../
I don't understand, why the javadoc for Resource#getRequestPath() doesn't simply reference section 2.6.1.3 of the spec and require a valid resource identifier instead of #getResourceName() for the result.
Let's simply change the javadoc here, if there is no good reason to leave it as is.
Loading the stylesheet from
http://localhost:8080/faces/javax.faces.resource/css/style.css would make it possible to reference the image with ../images/expert-draft-bg.png
Having this, you can simply use css files from the designer as you get them.
If all this comes to skinning, we could simply prefix the path with the skin as supposed by Hanspeters comment.
About all those minifying and combining comments. I think, this should not be part of the spec because it is a special case for css and js and no generic resource problem.
To address it a project similar to DeltaSpikr for CDI might also be useful for JSF.
Frank
Am 21.05.2012 um 16:12 schrieb Edward Burns <edward.burns_at_oracle.com>:
> EB-> There's basically three issues I want to get done before the Public
> EB-> Review Draft
>
> EB-> - 730 Flows
>
> EB-> - 971 MultiTemplating
>
> Frank, as soon as one starts thinking about 971-Multitemplating, one
> runs quickly into Jakob Korherr's 947-RelativeResourceHandler. We made
> some progress on this but I had to put it aside for other work deemed
> more important.
>
> Frank, can you please take a look at 947-RelativeResourceHandler and
> send me a private mail with a proposal for discussion, which I will
> refine and quickly, AND TRANSPARENTLY, turn around and send to the EG?
> In the name of transparency, you may CC, the EG if you must on this
> initial mail, but I feel doing so would unnecessarily muddy the
> discussion, considering my promise to have the "real" discussion on the
> EG. If you do Cc the EG on this private mail to me, please make it
> clear that the EG should not reply to the mail and instead wait for the
> one that actually calls for discussion.
>
> Basically, the latest on the issue is that we need to craft the feature
> in light of a simplifying assumption that only prefix-mapped resources
> are supported.
>
> Thanks,
>
> Ed
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | homepage: | http://ridingthecrest.com/