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.
Original status: 1-Dispatched; Suggested Status: NEW Original submitter: sakthivelg Description: http://forum.sun.com/jive/thread.jspa?threadID=96739 Design tab not available for JSP Page Hi everyone! I'm currently in the process of trying out JSC for my company, to see whether it's something that we should use in the future or not. We have a standard way to setup our project structure, so I tried to setup the project in JSC in a way that confirms to our structure. The problem I have now is that the jsp pages are not supposed to be in the *JSC web* directory according to my company guidelines, but JSC refuses to recognise them as "designable" JSP pages when I put them anywhere else but there. I found a post that mentions this here: http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=60893 Does anyone have an idea how I could get the "Design" tab to show up even if I don't use the JSC default project structure? Thank you for any tips in advance! ----- I guess this forum user is from CITADON. They have given up on Creator for this very same reason. ----------- Exceprt from Matt's CITADON Customer visit report 2. Citadon actually requested an option for JSPs not to use an accompanying page bean. Given that they are fairly new to JSF, it was difficult to explain that we do need some predictable place to put lifecycle and action/valuechange methods (and occasionally to initialize certain properties), not to mention that in some cases it is more convenient to access the component objects rather than create binding targets, etc. etc. Nonetheless, I did convey that I would record the request in case we hear it repeated in the future from any other customers. 3. Given my answer to #2, they followed up by requesting that the New Page dialog have an option for specifying the package of the page bean. Essentially, they want their JSPs to reside all that the same level, but for the page beans to have an independent hiearchy, for purposes of organizing the application into different parts, and particularly to simplify collaboration. (I was somewhat surprised they did not want the JSP hierarchy to mirror the page bean hierarchy, but I do understand the overall motivation.) ------------