[MYFACES-2629] Accept abstract FaceletContext, do not force AbstractFaceletContext

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0.0-beta-3
• Component/s: General, JSR-314
• Environment: Tomcat 6.0+, MyFaces 2.0.0-beta3 API/Impl.
• Assignee: Leonardo Uribe
• Reporter: Lewis Gass
• Created: 29/Mar/10 02:52
• Updated: 15/Dec/15 20:55
• Resolved: 15/Dec/15 20:55

Description

I am the main coder on the Gracelets project (http://gracelets.sourceforge.net/) and have recently began integration of Groovy with JSF 2.0. In order for Gracelets to harness the already existing Facelets libraries it needs access to the TagLibrary class and the actual libraries loaded by the JSF 2.0 implementation. Since that library is not part of the JSF 2.0 public API, I have to write an extension for each different JSF 2.0 implementation in order to load them. I have been able to successfully integrate with the SUN RI with minimal code. However, in MyFaces Core implementation this code appears on line 135 of the org.apache.myfaces.view.facelets.tag.jsf.ComponentTagHandlerDelegate:

AbstractFaceletContext actx = (AbstractFaceletContext) ctx;

Gracelets has its own FaceletContext (which is part of the public API) in order to mimimize integration between different JSF 2.0 implementations. Since in MyFaces this is forced to be a particular sub class here, it breaks portability. Is there anyway this can be avoided?