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.
[ BUILD # : 200810150201 ] [ JDK VERSION : 1.6.0_06 ] Hi, When I try to open or edit my index.jsp, which I created with previous builds of NB65, nothing happens. NetBeans' messages.log shows a strange exception about some object that can't be found, but that object/file is existing in the presented location. I checked in NB as well as in Windows' explorer. I'll attach the messages.log. Iwan
Created attachment 72043 [details] NetBeans' messages.log showing the exception mentioned.
Hi, Could you, please, provide more info, how did you get to that state: Did you manipulate the project files (especially the index.jsp), somehow before (deleting, renaming, moving)? Is that file actually present on the disk (the one the exception message points to)? Would it be possible to attach your project to this issue? Thanks.
Did you modify the project outside of the IDE? Visual Web does not default create the JSF page named 'index.jsp'! I think your modification just makes Visual Web confused and tries to open it as a Visual Web page. Quy, the exception is coming from jsfloader that you may know better.
I looked into code, and from the exception can guess following: There are various scenarios possible. 1) In case there is the corresponding java (or jsp) missing, then the opposite file shouldn't be loaded as JSF data object. 2) If it did exist before, and somehow the corresponding file disappeared, then also the remaining DO needs to be invalidated, so it could be reloaded as a plain file 3) if there is other conflicting data loader, somehow getting in front of one of our JSF loaders, then it might cause this problem. From the code, it looks like it could be 3), but it needs to be verified. If that's the case, there should be at least a better handing of invalidation of such corresponding DO (for better detection of issues like this). However, ultimately, the conflicting data loader would need to adjust.
It is likely the third scenario; from examining the code, another exception would have been thrown if it were either of the other two cases. Originally, the invalidation was in place to reload the DataObject if it was initialized incorrectly during page creation. However, I don't see how we can do better invalidation if another DataLoader is the culprit, since any subsequent DataObject.find() call would get the incorrect DataObject as well.
Created attachment 72055 [details] jar with additional logging
Try unzipping this into your NetBeans installation directory (it should replace a file under visualweb2/modules) and running again. It should provide additional logging when you run into the error; if you could attach the messages.log file for that run, it would be very helpful.
The page was created in NB61. I have changed it in earlier versions of NB65. All work on it has always been using NB. The page shows correctly in GF2v2ur2 (GF) and I have been able to work on it recently, although I can 't remember the build of NB65. As I pointed out in the original report, the file exists. It is physically on disk and it shows in NB's project as well as file view. I just can't open it. FYI: both the .JSP and the .JAVA exist. I didn't manipulate the project files outside of NB. Even inside of NB I didn't do anything with them since the last time I was able to edit the file. If anything was changed to the project files, it was done by NB automatically. Btw, I just tried it in build 200809040201 and there it all works perfectly. Iwan
Here's an update on when things went wrong... When I open the file in build 200809290201 it works. When I try it in 200810101401 the file doesn't open. This might give you a timeline as to when things went wrong. Iwan
Created attachment 72088 [details] The requested messages.log
It looks like either the visualweb java loader failed to recognize the file or somehow the relative position between the vw java loader and the default java loader was changed. I haven't been able to reproduce this problem either with new projects or projects created in NB 6.1. Is it possible to attach the project you're using?
Works in RC1 again. Iwan
reported as working in rc1, and hope later