Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.3
    • Fix Version/s: 1.0.4
    • Component/s: None
    • Labels:
      None
    • Environment:
      jdk6u10

      Description

      run the application created and browse the main page.

      Fatal Error occurred
      [Fatal Error] :-1:-1: Premature end of file.

      see the attached app.

      Thanks,
      Daniel.Sun

      D:\_DEV\grails_apps\Grails103>grails run-app
      
      Welcome to Grails 1.0.3 - http://grails.org/
      Licensed under Apache Standard License 2.0
      Grails home is set to: D:\D\MY_DEV\grails-1.0.3
      
      Base Directory: D:\_DEV\grails_apps\Grails103
      Note: No plugin scripts found
      Running script D:\D\MY_DEV\grails-1.0.3\scripts\RunApp.groovy
      Environment set to development
        [groovyc] Compiling 1 source file to C:\Documents and Settings\Daniel\.grails\1.0.3\projects\Grail
      s103\classes
           [copy] Copying 1 file to C:\Documents and Settings\Daniel\.grails\1.0.3\projects\Grails103
      Running Grails application..
      2008-06-10 21:49:55.631::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
      2008-06-10 21:49:55.787::INFO:  jetty-6.1.4
      2008-06-10 21:49:56.06::INFO:  No Transaction manager found - if your webapp requires one, please co
      nfigure one.
      2008-06-10 21:49:56.428:/Grails103:INFO:  Set web app root system property: 'Grails103-development-0
      .1' = [D:\_DEV\grails_apps\Grails103\web-app\]
      2008-06-10 21:49:56.428:/Grails103:INFO:  Initializing log4j from [file:C:\Documents and Settings\Da
      niel/.grails/1.0.3/projects/Grails103/resources/log4j.properties]
      2008-06-10 21:49:56.459:/Grails103:INFO:  Initializing Spring root WebApplicationContext
      [0] spring.GrailsWebApplicationContext Refreshing org.codehaus.groovy.grails.commons.spring.GrailsWe
      bApplicationContext@1364ee5: display name [org.codehaus.groovy.grails.commons.spring.GrailsWebApplic
      ationContext@1364ee5]; startup date [Tue Jun 10 21:49:59 CST 2008]; parent: org.springframework.web.
      context.support.XmlWebApplicationContext@177ab84
      [0] spring.GrailsWebApplicationContext Bean factory for application context [org.codehaus.groovy.gra
      ils.commons.spring.GrailsWebApplicationContext@1364ee5]: org.springframework.beans.factory.support.D
      efaultListableBeanFactory@b0c5a
      2008-06-10 21:50:03.050:/Grails103:INFO:  Initializing Spring FrameworkServlet 'grails'
      2008-06-10 21:50:03.126::INFO:  Started SelectChannelConnector@0.0.0.0:8080
      Server running. Browse to http://localhost:8080/Grails103
      2008-06-10 21:50:10.296:/Grails103:INFO:  GSP servlet initialized
      [Fatal Error] :-1:-1: Premature end of file.
      

        Activity

        Hide
        Steve Tekell added a comment -

        not just Firefox 3

        I get this with Firefox/2.0.0.14 (Linux)
        Not on every page, but when displaying XML.

        I am using
        withFormat { xml { render(contentType:"text/xml")

        { ... }

        } }

        Show
        Steve Tekell added a comment - not just Firefox 3 I get this with Firefox/2.0.0.14 (Linux) Not on every page, but when displaying XML. I am using withFormat { xml { render(contentType:"text/xml") { ... } } }
        Hide
        Hank Gay added a comment -

        This error also appears with Opera 9.5 on every page I've tested.

        Show
        Hank Gay added a comment - This error also appears with Opera 9.5 on every page I've tested.
        Hide
        Graeme Rocher added a comment -

        Fixed

        Show
        Graeme Rocher added a comment - Fixed
        Hide
        Graeme Rocher added a comment -

        Just a few implementation notes. We were defaulting to a q value of 0, which is incorrect according to the spec. So we now default to 1.0 which gives the correct precedence order in Firefox 3, but incorrect in Firefox 2. However, more specific XML types like application/xhtml+xml now take precendence over less specific ones if they have the same q value so this fixes the issue in Firefox 2.

        If others have problems in different browsers please open separate issues.

        Show
        Graeme Rocher added a comment - Just a few implementation notes. We were defaulting to a q value of 0, which is incorrect according to the spec. So we now default to 1.0 which gives the correct precedence order in Firefox 3, but incorrect in Firefox 2. However, more specific XML types like application/xhtml+xml now take precendence over less specific ones if they have the same q value so this fixes the issue in Firefox 2. If others have problems in different browsers please open separate issues.
        Hide
        Graeme Rocher added a comment -

        Bulk closing bunch of resolved issues

        Show
        Graeme Rocher added a comment - Bulk closing bunch of resolved issues

          People

          • Assignee:
            Graeme Rocher
            Reporter:
            Daniel.Sun
          • Votes:
            14 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development