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 noticed that in the 3.6 beta, you can no longer create a new JSP file under a filesystem with the new file wizard unless you have a web module mounted. Now this is a bit of overkill, because not every developer uses this type of structure. Our application makes extensive use of JSP's, but because of the way it accesses our database, there is no way to execute/debug JSP's from within the IDE, they must be uploaded to a test server for testing/debugging. Also, 3.6 no longer allows you to compile a JSP in the editor, which is another shortfall. Being able to quickly compile a JSP is useful to quickly debug any syntax errors and the like, without having to actually go through the whole JSP execution process. And again, that is dependent upon the developer being able to mount and make use of a web module, which I do not. In short, the forcing of a mounted web module should be optional as was in 3.5.
Reassigning to web module.
As for JSP compilation, this is now replaced by JSP validation, which does roughly the same, only is faster and less buggy. I'll let Ana and Ann comment on the JSP creation issue.
The issue of JSP creation is logged as an enhancement here: 39670 For the bug submitter - could you include the basic structure of your web module (e.g. hierarchy of directories, and noting where WEB-INF, web.xml, JSPs, servlets, and other java classes and other config files (struts, etc) are ) Would help in getting more examples of how commonly ppl structure web apps and what we should support. thanks.
Created attachment 13388 [details] Directory structure of our web app
Ann, please look at the provided attachment that you requested and then close this bug as a duplicate of the JSP wizard Petr, did you file an RFE to reintroduce compilation? We've had a lot of requests for it. I'll bring it up in the JSP spec again.
Thanks for the input. marking duplicate of issue 39670 *** This issue has been marked as a duplicate of 39670 ***