Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If u really need to test the <code>.war</code> ,but i suppose your <code>grails run-app</code> command carried out successfully and application is running. Isn't? If it is!! I suggest you do the following : </p> <p>I suggest also the above error is a configuration problem to grails and tomcat on <strong>STS</strong> environment it self...seems to me...so ,</p> <pre><code>1. Install `Tomcat 6` Outside for Testing the `.war` after generating using grails console and the command below 2. Instead of running the war directly from the grails console try to generate a Test ,Development or a production environment `.war` package as follow . </code></pre> <p>N.B You need to have Environment Specific setting for Deployment in your <code>config.groovy</code> file under grails <code>conf</code> folder..</p> <p>continued ...</p> <pre><code>grails -Dgrails.env=development war </code></pre> <p>or ,Simply</p> <pre><code> grails deve war //here deve is referring to development environment u can do same for test and prod... </code></pre> <p>So.After you have successfully carried out the above steps ...it is time for you to collect you grains into a jar...so find the place of the war generated it is under <code>targets</code> folder on your <code>created grails application folder</code>.</p> <p>So ,after that <code>start</code> <code>manually</code> or <code>automatically</code> started <code>TOmcat6/7</code>.goto <code>webapps</code> server and copy the package you generated above...first Stop <code>Running Tomcat Server if any!</code>....Cheers!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload