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.
Access to the standard descriptor wizard for the various project types that have one (e.g. ejb project, ear project for sure, possibly app client and web) has been removed from Packaged Archive project. This is bad since if a user is using this project type to manage a JavaEE5 archive that does not include the necessary standard descriptors, they have no (nice) way to create the one if they need to override an annotation, or otherwise modify deployment information. Likewise, the spec at http://wiki.netbeans.org/wiki/view/NewFileWizard is wrong to exclude these wizards from this project type and should be fixed.
will fix for 6
Can you point me to a build number where this worked? I think it never did. Not in 5.5.1 anyway. ArchiveProject only supports template categories: private static final String[] APPLICATION_TYPES = new String[] { "sunresource-types", // NOI18N "XML", // NOI18N "simple-files" // NOI18N }; but templates for ejb-jar.xml and application.xml use: <file name="ApplicationXml"> <attr name="templateCategory" stringvalue="ear-types,ear-deployment-descriptor"/> <file name="ejbJarXml"> <attr name="templateCategory" stringvalue="ejb-types,ejb-deployment-descriptor"/> I guess ArchiveProject either needs to support these categories or better have links to these templates. Links would be better because you could then provide a different display name. That may be needed because both application.xml and ejb-jar.xml are called "Standard Deployment Descriptor" (not very helpful). If you find that this is really a regression and/or that you cannot fix it please reassign back to me.
Created attachment 45357 [details] png of Standard Deployment Descriptor support
It looks like the support to put an application.xml might not have been there in 5.5.1... The attached screen shot shows one way to get the Standard Deployment Descriptor to appear.
Pavel is right. this is not a regression.
OK. here is what I found after experimenting with no descriptor archives for some time. 1. a war without web.xml. the IDE doesn't have a wizard to create the web.xml. The user can create a web.xml. The user needs to restart the IDE to get the multiview editor to appear. need to switch to files view, if the module is stand-alone. 2. ejb jar without an a standard descriptor. has wizard. need to switch to files view to get to the wizard if the module is stand-alone. 3. app client without app-client.xml. an empty app-client.xml file gets created when the archive is expanded. this happens whether the module is stand-alone or part of an ear. 4. connector... not applicable. 5. the user can create an application.xml by hand in the Files view for ear files. Since there are work-arounds to get all the files necessary, I am lowering this issue to p3.
converting to an enhancement for the 7.0 time frame.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss