QeelwaEtech / omnifaces

Automatically exported from code.google.com/p/omnifaces
0 stars 1 forks source link

Faces Views doesn't work on all servers #125

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Using Faces Views in an application deployed to GlassFish 3.1.2.2 results in a 
situation that all JSF links to faces views scanned pages can't be resolved. 
Requesting a page directly results in a resource not found exception.

The feature does work on JBoss 7.1.3 and WebLogic 12.1.1. but also doesn't work 
on Geronimo v3.0.

Original issue reported on code.google.com by arjan.tijms on 26 Jan 2013 at 11:26

GoogleCodeExporter commented 9 years ago
Fixed in 
http://code.google.com/p/omnifaces/source/detail?r=5222215e78004b6a9e0e19512e36a
56e1e542487

As it appeared, the programmatic way to set a Facelets resource resolver via a 
servlet init parameter was at a too late point in time in a 
ServletContextListener. Moves most init code to a ServletContainerInitializer 
instead. 

However, since some parts of the init process have to be done after all 
ServletContainerInitializers have run (the mapping of the Faces Servlet), 
initing now happens in both the ServletContainerInitializer and the 
ServletContextListener.

Geronimo v3.0 doesn't work because it bundles a very old version of MyFaces 
that didn't support a Facelets resource resolver correctly (see 
https://issues.apache.org/jira/browse/MYFACES-2628). Maybe it's possible to 
work around this, but the bug seems to obscure to bother for the moment.

Original comment by arjan.tijms on 27 Jan 2013 at 12:28

GoogleCodeExporter commented 9 years ago
p.s. Faces Views was tested on MyFaces 2.1.10/TomEE 1.5.1 and appeared to work 
correctly there.

Original comment by arjan.tijms on 27 Jan 2013 at 12:30

GoogleCodeExporter commented 9 years ago
Issue 127 has been merged into this issue.

Original comment by arjan.tijms on 4 Feb 2013 at 4:13