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.
dev build from Jan 4, JDK 5.0, Linux I have my own set of projects: j2ee app + ejb prj + web prj. I created a DB schema file in the topdirectory of ejb project and want to add CMP EJB but can't see this schema in wizard. I can see it if I move it deeper in a project structure. Also actions available on tree nodes in this wizard should be banned.
Should xml files (other non-folder, non-dbschema files) also be hidden from this view?
Wizard scans for dbschema only in source roots and config files root (this restriction is there because for imported projects with different location of original and created project it's the only information about original location). There is definitely inconsistency between creating and selecting the dbschema. Should we restrict creation only to source roots/config file root, or should we try to scan all possible locations for dbschema?
I think we should restrict the creation to those 2 places, but maybe you should check with HIE to be sure.
The current UI spec says that the user should be able to browse the schema file using the file chooser (which means it can be anywhere) in CMP Beans wizard. Would it work this way? The other option is to open up a file browser (similar to Files window) that would allow the user to pick any file underneath the project. Please let me know which one of those options seems more appropriate.
Jano, if you check the current build, the spec is out of date, I think. There is no longer a file chooser, just a drop down of schemas in the project. Personally, I think we should restrict the list.
agree
Is there any problem with changing it to a file chooser? The other option is to limit the user to create dbschema files into a package which I think is quite strange. Especially if the generated schema files are put into the "conf" folder. Btw, is there any "best practice" where the schema files should go? Please let me know whether it is possible change the combo into a filechooser.
I see no problem.
I see a problem - it was a file chooser before and someone redesigned the wizard so it was not. Please find out who and why so we don't keep going back and forth =). Also, please see related issue 53017. I suggest an alternative - that source and config root (by project logical view names) are shown in the wizard combo box and that dbschema's new template only allow creation in those locations.
To rraccah: note that since the dbschema template is in the dbschema module, it doesn't know almost anything about the project. therefore it doesn't know where the project's configuration files root is located (let alone that the web project doesn't have a config root, it only has a src/conf folder, which isn't show under any name in the UI). The project sources can be obtained through ProjectUtils, but you can't find out which sources are test sources (in case don't want to show them).
Is this still an issue? I think we offered a few UI solutions of this problem. Please let me know what's the current state.
The wizard for CMP can simply scan the project root for dbschema files in addition to sources roots, no? This sounds like a simple change w/o UI impact that solves the original problem.
TM 5.0 -> TBD
Considering issue 54091 which limits the places where the user can create a dbschema file I think this is a WONTFIX. We want to encourage good practices, thus we should not encourage dbschema files outside src/conf and the source roots.
Since creating db schema by hand is not the typical scenario, I think this is not high priority, and suggest downgrading to P4.
Downgrading to P4.
Obsolete milestone, please reevaluate
closing as WONTFIX per previous comments. CMP is no longer actively supported.