[grails-2.0.0.RC3] Using g:include is breaking g:set on page scope

[cesararevalo]

This issue is related to grails version 2.0.0.RC3. After I upgraded
from 2.0.0.RC1 to 2.0.0.RC3 I started noticing that variables set at
the page scope withing GSPs, using the g:set tag, were not working.
After some investigation I realized the issue was caused by the
g:include tags within the same GSP file.

I am able to reproduce the problem with the following snippet of code
in a brand new grails project. After creating the project, I create a
file under the views/include/head.gsp and leave it empty. Then I
insert the following into the index.gsp:

       <g:include view="/include/head.gsp" />
       <h2>Set Test</h2>
       <g:set var="myVariable" value="${true}" />
       <g:if test="${myVariable}">
       <p>it is true</p>
       </g:if>
       <p>myVariable: '${myVariable}'</p>

The output from the above snippet should be:

       Set Test
       it is true
       myVariable: 'true'

But, instead what I get is the following:

       Set Test
       myVariable: ''

I am starting to think this is a bug. What do you think?

Thanks,
-Cesar

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Frank Greco]

We recently upgraded to Tomcat 6.0.35 recently, so I deployed our grails
war to $TOMCAT_HOME/webapps as usual.  It explodes correctly.  But when
I visit our site, I get the standard Tomcat page not our war deployment.

Any suggestions are appreciated.  I've tried a bunch of things... and I
*know* its something silly that I've forgotten... :(

Frank G

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Jason Davis]

anything in the catalina.out log?

On Thu, Dec 8, 2011 at 11:38 AM, Frank Greco <[hidden email]> wrote:

> We recently upgraded to Tomcat 6.0.35 recently, so I deployed our grails war
> to $TOMCAT_HOME/webapps as usual.  It explodes correctly.  But when I visit
> our site, I get the standard Tomcat page not our war deployment.
>
> Any suggestions are appreciated.  I've tried a bunch of things... and I
> *know* its something silly that I've forgotten... :(
>
> Frank G
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Jean Barmash 1]

Does it show up on URL/webappname?   so if you exploded it into /webapps/foo, do you see it at domainname.com/foo?

Jean

On Thu, Dec 8, 2011 at 1:49 PM, Jason Davis <[hidden email]> wrote:

anything in the catalina.out log?

On Thu, Dec 8, 2011 at 11:38 AM, Frank Greco <[hidden email]> wrote:
> We recently upgraded to Tomcat 6.0.35 recently, so I deployed our grails war
> to $TOMCAT_HOME/webapps as usual.  It explodes correctly.  But when I visit
> our site, I get the standard Tomcat page not our war deployment.
>
> Any suggestions are appreciated.  I've tried a bunch of things... and I
> *know* its something silly that I've forgotten... :(
>
> Frank G
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Frank Greco]

Nope.  I get a 404.

F

On 12/8/11 2:22 PM, Jean Barmash wrote:

Does it show up on URL/webappname?   so if you exploded it into /webapps/foo, do you see it at domainname.com/foo?

Jean

On Thu, Dec 8, 2011 at 1:49 PM, Jason Davis <[hidden email]> wrote:

anything in the catalina.out log?

On Thu, Dec 8, 2011 at 11:38 AM, Frank Greco <[hidden email]> wrote:
> We recently upgraded to Tomcat 6.0.35 recently, so I deployed our grails war
> to $TOMCAT_HOME/webapps as usual.  It explodes correctly.  But when I visit
> our site, I get the standard Tomcat page not our war deployment.
>
> Any suggestions are appreciated.  I've tried a bunch of things... and I
> *know* its something silly that I've forgotten... :(
>
> Frank G
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Frank Greco]

Thanks for helping Jason/Jean,

I do see an Error in the catalina.out log.
SEVERE: Error listenerStart  

I never saw that error in our previous deployments.  Any suggestions?

Frank G



On 12/8/11 1:49 PM, Jason Davis wrote:

anything in the catalina.out log?

On Thu, Dec 8, 2011 at 11:38 AM, Frank Greco [hidden email] wrote:

We recently upgraded to Tomcat 6.0.35 recently, so I deployed our grails war
to $TOMCAT_HOME/webapps as usual.  It explodes correctly.  But when I visit
our site, I get the standard Tomcat page not our war deployment.

Any suggestions are appreciated.  I've tried a bunch of things... and I
*know* its something silly that I've forgotten... :(

Frank G

---------------------------------------------------------------------

...
Dec 8, 2011 8:17:46 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Dec 8, 2011 8:17:47 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Dec 8, 2011 8:17:47 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [ -nonaming ]  { -help | start | stop }
Dec 8, 2011 8:17:52 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
Dec 8, 2011 8:17:53 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Dec 8, 2011 8:17:53 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1217 ms
Dec 8, 2011 8:17:53 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Dec 8, 2011 8:17:53 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
Dec 8, 2011 8:17:53 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Dec 8, 2011 8:17:53 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Dec 8, 2011 8:17:53 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ajug.war
loading security config ...
Dec 8, 2011 8:18:11 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Dec 8, 2011 8:18:11 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/ajug] startup failed due to previous errors
Dec 8, 2011 8:18:11 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [/ajug] created a ThreadLocal with key of type [org.codehaus.groovy.runtime.GroovyCategorySupport.MyThreadLocal] (value [org.codehaus.groovy.runtime.GroovyCategorySupport$MyThreadLocal@93068a]) and a value of type [java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@928095]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Dec 8, 2011 8:18:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
Dec 8, 2011 8:18:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Dec 8, 2011 8:18:11 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Dec 8, 2011 8:18:12 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Dec 8, 2011 8:18:12 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/25  config=null
Dec 8, 2011 8:18:12 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 18844 ms

[smakela]

Have you made any changes to the domain objects?
If you are using 'validate' as dbCreate your application will not start, if your
database is not up-to-date. You will end up with that Listener error.

- Sami
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[cesararevalo]

I created a JIRA for this here http://jira.grails.org/browse/GRAILS-8465. And it got solved, fix version 2.0 final.

-Cesar

[Frank Greco]

I haven't made any code changes whatsoever.  The only diff is Tomcat.

Frank

On 12/8/11 4:12 PM, Sami Mäkelä wrote:

> Have you made any changes to the domain objects?
> If you are using 'validate' as dbCreate your application will not start, if your
> database is not up-to-date. You will end up with that Listener error.
>
> - Sami
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>      http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email