This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The exception is thrown from the servlet wizard even before web application is deployed. This is likely caused by new "Compile on Save" feature as a reaction on web.xml change - that precedes servlet file creation. Exception (GlassFish V2): *Serverlog* ============================================================================= Cannot load org.me.calculator.client.ClientServlet reason : org.me.calculator.client.ClientServlet java.lang.ClassNotFoundException: org.me.calculator.client.ClientServlet at com.sun.enterprise.loader.EJBClassLoader.findClassData(EJBClassLoader.java:741)
What are the steps to reproduce? Is the deployment successful? Is it just message in log or something more serious?
Milan is this still valid?
The issue still exists, though it doesn't look very serious. Though, the web server complains the servlet class doesn't exists the deployment is accomplished correctly. This is related to all wizards related to file objects that are registered to deployment descriptor (web.xml). It's likely the following timing problem : - servlet file is created (using servlet wizard) - servlet compilation starts - web.xml file is modified (servlet element is added) - project is deployed (when Compile on Save is switched on) - since the compilation of the servlet is not finished yet - the error message appears - compilation is finished - project is deployed again The messages are confusing. Decreasing to P4, since the web project is deployed correctly in the end. However, the web project is being deployed twice unnecessarily.