3 Replies Latest reply on Sep 28, 2007 2:39 PM by seamdev

    Seam 2 CR1 upgrade issues

    seamdev

      On upgrading to Seam2 CR1, I am facing following 2 issues:

      Getting following message on application startup:

      INFO: JSF1027: [null] The ELResolvers for JSF were not registered with the JSP container.
      

      What is it supposed to mean? How should I fix it?


      Seam is generating invalid html response pages. Firefox gives following error:
      XML Parsing Error: not well-formed
      Location: http://localhost:7001/myproj/main.seam?cid=2
      Line Number 190, Column 9:</div><!DOCTYPE div PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" >
      --------^
      


      This page worked fine with seam 1.2.1ga. Is migration guide missing something about pages that depend on template.xhtml?

        • 1. Re: Seam 2 CR1 upgrade issues
          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

            The XML parsing in JSF 1.2 RI is stricter than in MyFaces.

            • 3. Re: Seam 2 CR1 upgrade issues
              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.