INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context 'null'ġ0:41:31,921 INFO using response state manager: .xmlhttp.ResponseStateManagerġ0:41:32,000 INFO Started J2EE application: file:/F:/jboss-4.0.5.GA-ejb3/server/default/deploy/jboss-seam-icefaces.earġ0:41:37,531 ERROR 10:41:37 AM .ELResolverInitPhaseListener populateFacesELResolverForJsp WARNING: Incorrect JSP version found, method getJspApplicationContext does not exist.ġ0:41:31,906 ERROR 10:41:31 AM .ConfigureListener contextInitialized 6- deployed jboss-seam-icefaces.ear and icefaces-ds.xml to the SunRI configured JBossAS 7- when I run, I get a NullPointerExceptionġ0:41:31,890 ERROR 10:41:31 AM .ConfigureListener isJspTwoOne
ĥ- built the ear, then removed the el-ri.jar and el-api.jar from the generated ear. Apparently the ICEFaces people don't seem to have a public bug tracking system (yet). See for example my post in "Seam doesn't play with ICEFaces".
#Icefaces download Patch#
The patch is trivial, however, when you patch this, you will run into other issues.
I encountered and investigated your problem: Section 10.4.5 of the JSF 1.2 specification states that you must "provide a constructor that takes a single argument of the appropriate type (in casu ViewHandler), if you want that the custom implementation receives a reference to the implementation that was previously fulfilling the role." The D2DViewHandler uses the "original" (id est the Default ViewHandler) ViewHandler in the calculateRenderKitId method, unfortunately, the D2DSeamFaceletViewHandler doesn't provide the aforementioned constructor, so the original view handler is never passed in this custom view handler, causing the NullPointerException (as we all know, constructors aren't inherited). Yes, I tried to combine JSF 1.2 with IceFaces and Facelets and came to the conclusion that this requires a lot of patching of IceFaces (despite Ted Goddard's claims elsewhere on this forum).
0 kommentar(er)
