Update on Q2 I have been running through the code, and was almost there and finally noticed that some URLs are returning a modification time of 0 specifically in Websphere. Coincidentally issue 336 was just fixed, and I have tested the change against my code, and the problem is fixed.
https://facelets.dev.java.net/issues/show_bug.cgi?id=336By the way, this is closely related to issue 286:
https://facelets.dev.java.net/issues/show_bug.cgi?id=286
which can probably be marked as complete too.
Thank you Sun / Oracle ;)
Ravi
On Wed, Apr 22, 2009 at 11:58 AM, Ravi Luthra
<coding@...> wrote:
We created a ResourceResolver that you specify in web.xml, as usual, but it can "chain" the capabilities of other resolvers. In that resolver we use the Java 6 API for Jar service loading, the ServiceLoader class, to find all "PrefixResourceResolver" classes. That interface supports resolveUrl and a method called getPrefix(), which returns something like "resource" or "generator". The different resolvers have special abilities depending on what we need.
Q1)
We are curious if there is going to be support for this kind of chaining/service lookup in JSF 2. If so we can simplify our structure.
Q2)
Also has anyone run into a problem specifically with Websphere 7 where the existence of a custom ResourceResolver in web.xml causes problems like this:
[4/22/09 11:20:32:728 PDT] 00000024 facelet I Facelet[/index.xhtml] was modified @ 11:20:32 AM, flushing component applied @ 11:20:32 AM
It makes our Ajax 4 JSF pages to not display correctly. If I remove the resourceresolver the problem goes away completely.
Thanks,
Ravi Luthra
