Grails 3.0.1 war file doesn't work from cli #605
Comments
mgkimsal
changed the title
|
You can use bootRepackage instead of war |
|
Absolutely no difference. a) never head of bootRepackage ever Still getting the same error - this is essentially a reopening of #583 which was closed. Apparently it works for everyone else, or it's only fixed in something after 3.0.1, but in 3.0.1 (pulled by gvm 2 days ago) I still get ERROR org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/].[grailsDispatcherServlet] - Servlet.service() for servlet [grailsDispatcherServlet] in context with path [] threw exception [Could not resolve view with name '/user/login' in servlet with name 'grailsDispatcherServlet'] with root cause But this works when just run as "grails run-app". Well, it doesn't work 100% - I still get errors re: "no session found for current thread" when trying to redirect inside an interceptor, which I'm about to create an issue for. |
I am not sure what scenarios would call for using it directly for a Grails app but you could. It is in the boot docs at http://docs.spring.io/spring-boot/docs/current/reference/html/build-tool-plugins-gradle-plugin.html JSB Jeff Scott Brown Autism Strikes 1 in 166 |
|
I can confirm error: ... 3.0.1 has introduced bugs .... $ grails create-app helloworld grade clean assemble worked in earlier 3.x Stack dump: |
|
I don't know how If I run the following commands, the app appears to work fine:
@davydotcom are you seeing any of this problematic behavior at your end? Thanks for the feedback. |
|
I just now noticed that you guys are reporting a problem executing the .war file, not the .jar file. I was testing the execution of the .jar file. |
|
when i tested the snap war was fine |
|
just did |
|
thats an old version of java 7 in the example not sure if thats why , also using gradle 2.3 at least yea? try with ./gradlew in the project maybe |
|
I get the same error with Hitting the browser at Current versions: Let me know if there is anything you want me to try, or info I can provide. Thanks! |
|
davydotcom >> "it worked like a dream ..."
I have now tested the war file again !!!!
the setting is: Conclusion: |
|
I have made a project with version 3.0.0.RC2 / 3.0.0.RC3 .. and it can run |
|
I did request a page got a proper response ill try a controller see what happens maybe |
|
I dont know if you guys have tried this but you may have something stuck in your cache from way back. I just tried a fresh grails 3.0.1 install on 2 different machines and both worked flawlessly. Maybe empty the ~/.grails/repository folder see if that helps at all |
|
Super David, thanks for the suggestion The stack dump is claiming |
Ok one last thought is to clear your ~/.m2 cacheDavid Estes On April 9, 2015 at 8:35:43 AM, Anders Kristian Andersen (notifications@github.com) wrote: Super David, thanks for the suggestion The stack dump is claiming — |
|
Hi David Please note that the helloworld-0.1.jar WORKS !!! |
right and WAR works for me as well so this is confusingDavid Estes On April 9, 2015 at 9:05:53 AM, Anders Kristian Andersen (notifications@github.com) wrote: Hi David Please note that the helloworld-0.1.jar WORKS !!! — |
|
All right. My war file contains... |
|
I don't know if this applies to this discussion or not, but since the problem includes the inability to find URL mappings, maybe it does. I've noticed that a new project places the UrlMappings.groovy file in The docs don't say where this file is supposed to be, but historically this file would have been found in I'm wondering if the various build tasks under discussion make assumptions (possibly different assumptions) about the location and proper destination for this file in the resulting war file. In the case of a plugin, treatment of mappings is also odd. If I place |
|
I have the same problem. When I run the application normally using grails run-app, it works fine. When I create a fat jar, and run with the |
|
PS: also tried with |
|
Hi all, @davydotcom gave me the tip how to fix it: don't run it from within the project. If I move the jar/war to /tmp, and run it from there, it works. Still a bug, but this is a good workaround! |
I think it has to do with the grails boot logic that determines if its running from within a container or a dev mode directoryDavid Estes On May 19, 2015 at 4:31:04 PM, Erik Pragt (notifications@github.com) wrote: Hi all, @davydotcom gave me the tip how to fix it: don't run it from within the project. If I move the jar/war to /tmp, and run it from there, it works. Still a bug, but this is a good workaround! — |
|
Hi @bodiam, that worked for me, too. Or just |
Can't reopen #583 but it's the same issue
Hitting the browser, I get...
ERROR org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/].[grailsDispatcherServlet] - Servlet.service() for servlet [grailsDispatcherServlet] in context with path [] threw exception [Could not resolve view with name '/index' in servlet with name 'grailsDispatcherServlet'] with root cause
javax.servlet.ServletException: Could not resolve view with name '/index' in servlet with name 'grailsDispatcherServlet'
The text was updated successfully, but these errors were encountered: