build-impl.xml:1031: The module has not been deployed

Question

I have been working on a Java web application and i am using SmartGwt on Netbeans 7.3 and out of a sudden I encountered this problem. I tried cleaning the build-impl.xml then restarting the IDE and I should say I have fairly low knowledge on this. Can someone please tell me why it is giving an error and how I can fix that?

The error message says :

nbproject/build-impl.xml:1031: The module has not been deployed. See the server log for details. 
BUILD FAILED (total time: 4 seconds)

Note: i am using Tomcat 7.0.34

Solution 1

may its so late but the response useful for others so : Sometimes, when you don't specify a server or servlet container at the creation of the project, NetBeans fails to create a context.xml file.

1. In your project under Web Pages, create a folder called META-INF.

Do this by right mouse button clicking on Web pages, and select:

New->Other->Other->File Folder

Name the folder META-INF. Case is important, even on Windows.

1. Create a file called context.xml in the META-INF folder.

Do this by right mouse button clicking on the new META-INF folder, and select:

New->Other->XML->XML Document

Name it context (NetBeans adds the .xml) Select Well-formed Document Press Finish

1. Edit the new document (context.xml), and add the following:

   <?xml version="1.0" encoding="UTF-8"?> 
   <Context antiJARLocking="true" path="/app-name"/> 
   

Replace app-name with the name of your application.

Now your in-place deployment should work. If not, make sure that the file can be read by everyone.

The context.xml file is specific to Tomcat. For more information about that file, see the Tomcat documentation at tomcat.apache.org.

Solution 2

Start your IDE with administrative privilege( Windows: right click and run as admin), so that it has read write access to tomact folder for deployment. It worked for me.

Solution 3

Take a look at the server logs!

I had been with this for hours. The awful Tomcat servlet is not very helpful neither but if you can see the stacktrace that should be enough.

For instance, I read the following error message there:

As you can see, the message was pretty clear and easy to fix :-)

Solution 4

• Check if there any other instance of the server is running already
• Check if the port that will be used by the server is free.

Solution 5

If you add jars in tomcat's lib folder you can see this error

View more solutions