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 76200 - Missing Configuration Files folder in Java Application project
Summary: Missing Configuration Files folder in Java Application project
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrei Badea
URL: http://j2ee.netbeans.org/nonav/docs/p...
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-11 10:27 UTC by jrojcek
Modified: 2008-01-16 17:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jrojcek 2006-05-11 10:27:39 UTC 
Newly created persistence unit is not visible in Java Project in Projects window. It should be visible 
underneath the Configuration Files folder. This folder should show up only if a persistence unit or 
database schema is created. See the spec in URL field.

Note that the spec also shows the manifest file underneath Configuration Files folder. It is questionable 
whether the manifest should be there because we don't want to have too many top level nodes in 
project view. So for now, it should only contain persistence nodes (PU, schemas) and it should only be 
visible if PU and schemas exist. 

I noticed that the PU shows up in META-INF "package". As this clearly isn't a package, it belongs 
underneath a separate Configuration Files node in Project window which provides a logical view.
Comment 1 Martin Adamek 2006-07-27 15:29:26 UTC 
Reassigning to java projects.
Comment 2 Milan Kubec 2006-08-15 13:37:01 UTC 
I'd rather postpone implementation of this to next release, since it's highly
probable that there will be general API for plugging nodes to project logical
views from other modules. See issue #72441.
persistence.xml file is accessible from logical view now.
Comment 3 Milan Kubec 2007-07-02 12:58:21 UTC 
Reassigning back, the API for adding node under project is available, see issue #72441.
Comment 4 Erno Mononen 2007-08-09 12:06:11 UTC 
So I guess what needs to be done is to implement a NodeFactory in j2ee/persistence to create the configuration files 
folder in Java SE projects.
Comment 5 Andrei Badea 2008-01-15 13:15:36 UTC 
Sorry, but I don't agree that this change would help the users, and I believe the problem is in the UI spec.

First, the Configuration Files nodes make much more sense in the Java EE projects where there are physical folders with
configuration files (for example, src/conf in EJB projects). Second, META-INF is a well-known directory, and I believe
most users know that persistence.xml resides in META-INF. If you hide META-INF (since you claim it is not a real
package) you will confuse users rather than help them. Third, if you make the logical view "too logical" it will be
actually harder to find things in it. The project is a physical structure after all, and we should hide it from users
only when it actually helps them (the package view is a good example).

Reassigning to you to fix the UI spec. Please reassign to the right person. Or I can fix the spec if you want.
Comment 6 jrojcek 2008-01-15 15:22:36 UTC 
If META-INF is a well known location for storing persistent unit and other things, I'm fine to keep it and don't implement the Configuration Files folder in Java 
SE projects. I suggest to close this issue.

The UI spec update is not necessary unless you want to update it. In that case please go on. Thanks.
Comment 7 Andrei Badea 2008-01-16 17:12:53 UTC 
Fixed the UI spec.

Checking in persistence-ui-spec.html;
/cvs/j2ee/www/docs/promog/persistence-ui-spec.html,v  <--  persistence-ui-spec.html
new revision: 1.13; previous revision: 1.12
done