Problems with ResourceResolver

Hi. I'm working in a project with Myfaces 2.0.5 and I have had a problem with a custom ResourceResolver. I have coded a ResourceResolver that dynamically builds an XHTML file when the engine asks him to resolve a certain URL. To achieve this, I have update the web.xml as follows:

Re: Problems with ResourceResolver

Hi, This seems to be an implementation issue of MyFaces. Please file a ticket in our JIRA at https://issues.apache.org/jira/browse/MYFACES Thanks! Regards, Jakob 2011/5/6 Juan Fernandez-Corugedo Igual jfcorug...@gmail.com: Hi. I'm working in a project with Myfaces 2.0.5 and I have had a

Re: Problems with ResourceResolver

Hi It is a known problem in JSF 2.0. see: https://issues.apache.org/jira/browse/MYFACES-2628 http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-893 Theorically there are 2 options: 1. Use MyFaces core 2.1.0-SNAPSHOT. 2. Use prefix mapping for your pages instead suffix mapping. Please

Re: Problems with ResourceResolver

Hi, we could provide a config parameter that enables this fix also in MyFaces 2.0.x. WDYT Leo? Regards, Jakob 2011/5/6 Leonardo Uribe lu4...@gmail.com: Hi It is a known problem in JSF 2.0. see: https://issues.apache.org/jira/browse/MYFACES-2628

Re: Problems with ResourceResolver

Hi Unfortunately, I already tried it without success. The problem is the algorithm for calculate the viewId when suffix mapping is used requires check if the physical resource exists, and there is no access from this part of the lifecycle to that object (because is a facelets object, so the only

Re: Problems with ResourceResolver

OK, agreed. Thanks for the explanation! Regards, Jakob 2011/5/6 Leonardo Uribe lu4...@gmail.com: Hi Unfortunately, I already tried it without success. The problem is the algorithm for calculate the viewId when suffix mapping is used requires check if the physical resource exists, and