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.
Currently, file-based deployment copies files from the J2EE module to the destination specified by the server. This allows to bypass the packaging step. However, as many servers can accept an arbitrary location of the files, this copy step is often redundant. It should be possible to just use the module directory specified by a devmodule directly by the server. This would save deployment time, and it would also allow the edit/save/refresh style of development of web content (JSPs, HTML files etc.) To make this possible, I suggest enhancing the semantics of methods FileDeploymentLayout.getDirectoryForNewModule(...) FileDeploymentLayout.getDirectoryForNewApplication(...) to return null. The null return value would indicate to the infrastructure that the server accepts any directory. Then the infrastructure would skip the copy step, and would pass the original directory to the plugin.
This might not be enough for other plugins which would need to make sure that the server specific deployment file(s) are in the correct location (i.e under the WEB-INF dir) of the app. So maybe an extra APIs has to be given to make sure the source directory structure has all the corret elements in place for a specific server.
Well, would it work if the config data is included in the correct location (e.g. WEB-INF/sun-web.xml) directly in the source structure? Also, in the Ant-based world there will be the Ant copy step, which will allow to put additional files in the right place.
change to fixed
Closed by accident, reopen.
In-place deployment is implemented and works well for webmodule against tomcat. Failure on initial deployment will not result in automatic general cleanup.