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 129021 - JSF Pages from Entity Classes generates useless packages with VW JSF
Summary: JSF Pages from Entity Classes generates useless packages with VW JSF
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Matthew Bohm
URL:
Keywords: RELNOTE
: 130862 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-03 15:32 UTC by Dan Kolar
Modified: 2008-03-26 05:34 UTC (History)
2 users (show)

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 Dan Kolar 2008-03-03 15:32:45 UTC
Product Version: NetBeans IDE Dev (Build 200803021202)
Java: 1.6.0_05; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)

1) Create Web project with VW JSF
2) Create Entity classes and persistence unit from simple database
3) JSF Pages from Entity Classes -> Add All -> Next
4) Fill "jsff" into "JSF Page Folder" -> Finish

Now all Converter/Controller classes are created in {project name} package, but a whole bunch of empty packages is
created, one for every entity class, with package name {project name}.jsff.{entity class name}
Comment 1 Matthew Bohm 2008-03-03 15:48:41 UTC
Similar to issue 127291, except this one deals with the JSF Pages Folder field rather than the Package field.
Comment 2 Matthew Bohm 2008-03-21 21:02:41 UTC
Actually, the defining maneuver here is selecting visual web JSF rather than just JSF. Reproducible.
Comment 3 Matthew Bohm 2008-03-22 10:42:41 UTC
The obvious cause would appear to be that there is an insync listener responding to the creation of each JSP folder by
creating a corresponding Java package. In this case, because the operation is not related to visual web functionality,
the listener should not do so. Perhaps the listener can be temporarily removed prior to creating the JSP folder and then
restored after the JSP folder is created. Copying sandipchitale and deva for advice on how to achieve this or a similar
solution.
Comment 4 Matthew Bohm 2008-03-24 04:52:40 UTC
*** Issue 130862 has been marked as a duplicate of this issue. ***
Comment 5 Matthew Bohm 2008-03-26 05:34:31 UTC
I've been advised by sandipchitale and deva. The behavior is a limitation in the vw architecture; effectively, it does
not have a concept of non-vw jsp folders existing. Even if we temporarily remove the listener, the next time the project
is opened, the corresponding java packages will be created. Not much to be done. They do no harm; I consider this a
release notes candidate.