This content has been marked as final.
Show 3 replies
-
1. Re: Seam 2 CR1 upgrade issues
seamdev Sep 25, 2007 6:22 PM (in response to seamdev)I solved the XML Parsing Error. It was due to one of the xhtml file being included from template.xhtml. Header for included files seems to have changed, see header of conversations.xhtml in the jpa example in seam2 and seam1.2.1. Perhaps it should be documented in seam 2 migration guide.
-
2. Re: Seam 2 CR1 upgrade issues
pmuir Sep 26, 2007 7:28 AM (in response to seamdev)The XML parsing in JSF 1.2 RI is stricter than in MyFaces.
-
3. Re: Seam 2 CR1 upgrade issues
seamdev Sep 28, 2007 2:39 PM (in response to seamdev)
will like to know what do the following messages in log mean..INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b16-p02) for context 'null'
com.sun.faces.lifecycle.ELResolverInitPhaseListener populateFacesELResolverForJsp INFO: JSF1027: [null] The ELResolvers for JSF were not registered with the JSP container.