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.
Summary: | [69cat] java.io.FileNotFoundException: C:\Users\Javier\Documents\NetBeansProjects\Xinco\XincoWebApp\nbproject\jax-ws.xml (The system cannot find the file specified) | ||
---|---|---|---|
Product: | platform | Reporter: | javydreamercsw <javydreamercsw> |
Component: | Filesystems | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.0 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 173359 |
Attachments: | stacktrace |
Description
javydreamercsw
2010-10-21 12:17:57 UTC
Created attachment 102542 [details]
stacktrace
This exception is not consequence of error in IDE . This is result of external modification of the project. jax-ws.xml file was deleted between two invocations in the source code: successful finding this file on FS and access to this file for its read. Some external process deletes jax-ws.xml at the same time when project opens. If you are able to reproduce this bug then please provide exact steps of reproduction. Steps to replicate: 1. Check out source from: https://xinco.svn.sourceforge.net/svnroot/xinco/trunk 2. Open the XincoWebApp project and all related projects 3. Close the 3 projects 4. With the IDE still open delete the downloaded projects and in the same place check out from: https://xinco.svn.sourceforge.net/svnroot/xinco/branches/2.0 5. Open the XincoWebApp project and all related projects In the scenario above it seems to be some cache issues as the project still shows the jar dependencies from the project on step 1. This happened at the same time issue #191211 happened. They might be related. Thanks for detailed steps of reproduction. It really looks like some cache problem. But this is not WS bug. There are two calls : FileObject fileObject = project.getProjectDirectory().getFileObject() and if ( fileObject!=null) { File file = FileUtil.toFile(fileObject); // read file } variable file equals null . But it should not be because is in case of file absence previous call for FileObject should return null. Reassign to filesystem functionality. Probably related to the fact that right now the state in the memory is not updated automatically with the real state on the disk. *** This bug has been marked as a duplicate of bug 190462 *** |