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.

Bug 108079 - Fix Page Fragments to be placed in WEB-INF
Summary: Fix Page Fragments to be placed in WEB-INF
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: _ sandipchitale
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-25 21:33 UTC by _ krystyna
Modified: 2008-12-10 19:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ krystyna 2007-06-25 21:33:08 UTC
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.
Comment 1 Chris Kutler 2007-06-28 15:57:29 UTC
This was a user initiated bug. See the comments section in this blog entry:
http://blogs.sun.com/divas/entry/page_fragment_tips
Comment 2 Mark Dey 2007-07-12 14:57:17 UTC
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.
Comment 3 Chris Kutler 2007-08-14 00:43:03 UTC
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/
Comment 4 _ sandipchitale 2007-10-26 04:34:05 UTC
We will look at it after 6.0.
Comment 5 Peter Zavadsky 2008-12-10 19:21:02 UTC
No current plan to resolve it. Moving to 'later'.