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.
I have a Java free-form project with several folders which contain JSP files. When I open some of those files I can see that highlighting work fine, but, unfortunately, intellisense does not at all. That means when I press Ctrl-Space keys I always get "no suggestions" popup message. Can anyone help? OS: MS Windows 7 x64
Reassigning to Freeform
Does everything works fine for Java files? Classpath configuration would be first culprit I would have a look at.
Everything works fine with .java files. I have two separate source folders for .java and .jsp files, but they use absolutely the same classpath (checkbox 'Separate Classpath for Each Source Package Folder' disabled in settings). In .jsp files I even cannot get auto-complete for standard Java classes inside the scriplets.
Created attachment 114239 [details] Java editor
Created attachment 114240 [details] JSP editor
Created attachment 114241 [details] Settings
I have added some screenshots to show what I described earlier.
I cannot reproduce the problem. A test project illustrating the issue would help. On JSP editor screenshot it looks like JSP files are under Java packages?? That would be wrong - they should be under Web Document root.
I don't have that exact project right now (it was from the previous job), but as far as I remember, it was an ant-based project, definitely not a web one. Though the .jsp files were in the directory where they were supposed to be for the correct .war file creation. Regardless of what the project was and even whether the .jsp files were located in some strange directories, I happen to disagree with the "that would be wrong" statement. If you open a .jsp file, it is expected to be handled as a .jsp file with regard to the intelligence support. As you can see from the screenshots, the highlighting worked fine for the .jsp file. Please try to reproduce it by creating an ant-project out of NetBeans with jsp files in it. Then open that project in NetBeans ("create from an existing build.xml file" or something like that, as far as I remember), and I believe you would reproduce the issue just fine.
PS In the initial description I was writing "a Java free-form project" (I think this is one of the options in NetBeans to create a project), you can also try that one. And please note that essentially in such projects people can have .jsp files in whichever folders they want to.
I should have said "that would be wrong in context of NetBeans IDE because JSP files are expected under Web Document Root". I agree that users can put there files anywhere they want but that does not mean that IDE will be able to assist them always equally well. Putting JSP into a Java package is like putting Java file into a non-Java package and expecting that Java editor will be able to work, provide code completion, compile file on save, etc. Sometimes maybe but in many cases it will be a failure. And in such cases I too would suggest to place Java files under java package to resolve the issue. :-) Anyway it sounds like you do not have this problem anymore and while possibly the defect is still valid and exists it is not worth fixing it. IMO.
That's correct, I am not working with JSP right now, and using NetBeans for plain Java only. Regarding your last phrase, my personal opinion is that if the NetBeans dev team is going to make the product better and improve its quality, it's worth fixing any bug, especially taking into account that not all your customers file bugs (they can be too lazy or for any other reason, it doesn't really matter). My point here is that I might be not the only person who faced that issue, and if I personally don't work with JSP at the moment, maybe there are people who do. PS Just my opinion, of course...
In general I agree with what you are saying. We do not lack bug reports though. :-) And out of hundreds of P3 reports some are more severe and some less. This one fits the less category.
Okay, good, so let's close it then for now. If I happen to face this issue again in future, I will just find this bug and reopen it attaching a sample project, so you would be able to reproduce it.