myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] Commented: (MYFACES-2628) Facelets ResourceSolver cant work
Date Mon, 02 Aug 2010 19:57:20 GMT


Leonardo Uribe commented on MYFACES-2628:

Because to resolve suffix mapping when the view is resolved it is necessary to check if the
resource exists or not. If a request receive something like /mypage.jsf, it is necessary to
check if the resource is /myfaces.xhtml or /myfaces.jsp or /myfaces.jspx, and this is done
checking if the resource file exists or not. Right now, if someone overrides the ResourceResolver,
the current algorithm continues looking for the resources on the same locations, ignoring
ResourceResolver interface.

Maybe we can use ResourceResolver.resolveUrl for this, if it returns null the resource does
not exists otherwise it exists, but there is no standard way to expose the current ResourceResolver

> Facelets ResourceSolver cant work
> ---------------------------------
>                 Key: MYFACES-2628
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-3
>         Environment: tomcat 6.0.20, java 1.6(mac osx), 
>            Reporter: Mark Li
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> In facelets 1.1.14, I can load page from classpath via ResourceSolver, 
> by in myfaces 2.0.0-beta-3, I cant do this, because 'DefaultRestoreViewSupport.checkResourceExists'
method check the resource exists using 'servletContext.getResource(path);', should do some

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message