You need to check whether the context root element for the web module in the application.xml file has been changed correctly, which in the META-INF directory of your EAR has been changed correctly.
An example would look like this:
<?xml version="1.0" encoding="UTF-8"?> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" id="Application_ID" version="6"> <display-name>TestProject</display-name> <module> <web> <web-uri>TestProjectWeb.war</web-uri> <context-root>testproject</context-root> </web> </module> <module> <ejb>TestProjectEJB.jar</ejb> </module> </application>
In this example, the web module should be accessible under / testproject of the server you are deploying to, so in your case http://localhost:8080/testproject .
(If you want to deploy it to the root directory of your server, you can leave the context root element empty: <context-root></context-root> .)
If you really see that your action in Netbeans has correctly modified this file, it could be a deployment problem, for example, BalusC. Check the location to which the EAR is deployed, and manually verify that the version of the deployed value has the correct value.
Arjan tijms
source share