-
Aug 28th, 2010, 12:24 AM
#1
Error deploying to Google App Engine
I have downloaded the new Spring Roo 1.1.0.M3 and I have created a real simple project. After I exit roo shell I run the mvn gae:deploy command and get the following error.
Steps
roo> project --topLevelPackage com.tenminutes
roo> persistence setup --provider DATANUCLEUS --database GOOGLE_APP_ENGINE
roo> entity --class ~.Timer --testAutomatically
roo> field string --fieldName message --notNull
roo> hint controllers
roo> controller all --package ~.web
roo> selenium test --controller ~.web.TimerController
roo> perform tests
roo> perform package
roo> perform eclipse
roo> quit
I changed the application name in appengine-web.xml.
c:\ mvn gae:deploy
Something is not setup correctly in the web.xml file but not sure.
com.google.apphosting.utils.config.AppEngineConfig Exception: Welcome files must be relative paths: /
at com.google.apphosting.utils.config.WebXml.validate (WebXml.java:115)
at com.google.appengine.tools.admin.Application.<init >(Application.java:96)
at com.google.appengine.tools.admin.Application.readA pplication(Application.java:128)
at com.google.appengine.tools.admin.AppCfg.<init>(App Cfg.java:107)
at com.google.appengine.tools.admin.AppCfg.<init>(App Cfg.java:58)
at com.google.appengine.tools.admin.AppCfg.main(AppCf g.java:54)
at net.kindleit.gae.EngineGoalBase.runAppCfg(EngineGo alBase.java:178)
at net.kindleit.gae.DeployGoal.execute(DeployGoal.jav a:38)
at org.apache.maven.plugin.DefaultPluginManager.execu teMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeStandaloneGoal(DefaultLifecycleExecutor.j ava:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoalAndHandleFailures(DefaultLifecycleExe cutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeTaskSegments(DefaultLifecycleExecutor.jav a:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMav en.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven .java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:3 62)
at org.apache.maven.cli.compat.CompatibleMain.main(Co mpatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(L auncher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher. java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.ja va:375)
-
Aug 28th, 2010, 06:40 AM
#2
Here, same procedure, same trouble.
-
Aug 28th, 2010, 01:29 PM
#3
Have you tried running it under tomcat? It is working under tomcat for me.
mvn tomcat:run
-
Aug 29th, 2010, 01:20 PM
#4
In web.xml, change the <welcome-file> tag from "/" to "index"
This is something that changed from 1.1.0.M2 to 1.1.0.M3 for some reason...
-
Aug 29th, 2010, 03:28 PM
#5
Could this be a bug or is it something I'm doing wrong?
-
Aug 30th, 2010, 07:22 AM
#6
I think it's a bug. I get the same error.
Modifying the web.xml as Justin says works though.
-
Sep 1st, 2010, 07:18 AM
#7
Should this issue be file on the issues tracker? If so I can file it if we need to.
Thanks
Zach
-
Sep 1st, 2010, 01:28 PM
#8
It sounds like you get it to work on App Engine after modifying the <welcome-file>? I get the same error but after changing <welcome-file> to index, i get another error (does anybody know how to avoid this one?):
org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'org.springframework.web.servlet.resource.DefaultS ervletHttpRequestHandler#0': Initialization of bean failed; nested exception is java.lang.IllegalStateException: Unable to locate the default servlet for serving static content. Please set the 'defaultServletName' property explicitly.
at org.springframework.beans.factory.support.Abstract AutowireCapableBeanFactory.doCreateBean(AbstractAu towireCapableBeanFactory.java:527)
at org.springframework.beans.factory.support.Abstract AutowireCapableBeanFactory.createBean(AbstractAuto wireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.Abstract BeanFactory$1.getObject(AbstractBeanFactory.java:2 91)
at org.springframework.beans.factory.support.DefaultS ingletonBeanRegistry.getSingleton(DefaultSingleton BeanRegistry.java:222)
at org.springframework.beans.factory.support.Abstract BeanFactory.doGetBean(AbstractBeanFactory.java:288 )
at org.springframework.beans.factory.support.Abstract BeanFactory.getBean(AbstractBeanFactory.java:190)
at ...
-
Sep 1st, 2010, 02:18 PM
#9
Someone sent me the follow message. I will try it this evening. I have the same case. Let me know if it works.
Hey guys, I FOUNDED. I have the same problem. I use win 7 64bit and of course I install JDK of 64 bits... and have the problem...
To solve this issue, install a jdk of 32 Bits, and set your environment variable JAVA_HOME, to the new jdk installed.
-
Sep 1st, 2010, 10:13 PM
#10
Tried change everything to 32 bit and still no luck. I did post something on twitter and google app engine google group to see anybody else has an answer.
Zach
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules