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: | Fix Page Fragments to be placed in WEB-INF | ||
|---|---|---|---|
| Product: | obsolete | Reporter: | _ krystyna <krystyna> |
| Component: | visualweb | Assignee: | _ sandipchitale <sandipchitale> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | Sun | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
This was a user initiated bug. See the comments section in this blog entry: http://blogs.sun.com/divas/entry/page_fragment_tips jspf pages require a corresponding backing bean with a package name that reflects a location relative to the root web folder. This makes WEB-INF problematic as a destination folder for jsp/jspf files. Quite a bit of work is required to remove this constraint. Since there is a workaround, priority can be reduced. Here are the code conventions that are confusing our users. They try to follow these conventions and VWP won't let them. http://java.sun.com/developer/technicalArticles/javaserverpages/code_convention/ We will look at it after 6.0. No current plan to resolve it. Moving to 'later'. |
To possibly be fixed in a future release: Customer issue: Sun recommends putting jspf page fragments into a WEB-INF/jspf folder so that the fragments are not directly accessible. But you can't create a "Page Fragment" in WEB-INF with VWP (don't know about JSC) as you get an error "Name WEB-INF is an invalid folder name. Please specify a name that is a legal Java identifier". Workaround: You are correct that the IDE tries to put the backing bean in the WEB-INF package and package names cannot have dashes. Winston Prakash suggests that you use a Security Filter to disallow access to page fragments from the regular web page area.