Deployment error on tcServer

By deployment I mean deploying war in tcServer v6. Running application by 'grails run-app' is working just fine.

Does the same application deploy fine on the tc6 without the jQueryplugin?

I've been deploying same application with jquery plugin 1.3 and it worked ok. Problem first occured on CloudFoundry but I've replicated it on my local dev machine.

This issue isn't specific to Blazej's application. It can be reproduced easily by doing:

grails create-app crashTest
cd crashTest
grails install-plugin jquery
grails dev war
cp target/crashTest*.war /path/to/tomcat/webapps

I think that Glassfish v3 is affected as well. I've tried to deploy application and same error occured.

If memory serves, Glassfish V3 is using tomcat/catalina as the app container, so it's not a huge surprise. The surprise, to me, is that grails 1.2 isn't crashing even though grails is using tomcat as its embedded container when you do grails run-app.

tc 5.5 works fine here. i'll try glassfish 3 und tc6 next

does grails use a tc6 container?

I believe that grails run-app is running on Tomcat 6-Snapshot. At least that's what it shows on error pages.

Well.. I cannot agree that it works for tomcat 5.5. I've created app from scratch and it fails same as before. Test case provided by Jonathan is reproducing this bug on both tomcat v5.5 and tomcat v6.

Occours with Websphere also (http://jira.codehaus.org/browse/GRAILSPLUGINS-1888)

I will try to get some time free within the next days and check everything in detail.

It appears caused by having the typed "GroovyClassLoader classLoader" field exposed to auto-injection in JQueryTagLib class which causes the class conversion erorr in spring since the classloader in war environment will not be a GroovyClassLoader. A quick fix will be changing the classLoader field to private hence removing the getter and setter generated by groovy, or simply inline the classLoader field since its only used to load jqueryConfig.

I have tested the private scope change on jetty and tomcat with run-war and war target, it seems to be a valid solution.

Tried it and seems to work fine, thanks.

I'll provide a new release today bundled with jQuery 1.4.1

Cheers

I can confirm that the jquery plugin version 1.4.1.1 now works with Websphere 6.1

The problem is in constructor, so I propose another fix:
GroovyClassLoader classLoader = new GroovyClassLoader((ClassLoader) getClass().getClassLoader());

Here we specify the constructor parameter's type and everything goes ok.
Tested at jetty via war (before fix got the same error as author).