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.
I configured a WAS 6.0 server in Netbeans, pointing at the local app server installation from a copy of Rational Application Developer 7. I created a new web app project, targetting that server. I edited the web.xml and added a resource reference for a DataSource "jdbc/datamart". After saving that, I opened the ibm-web-bnd.xmi and added a new Resource Reference Binding. Two things struck me: the Name in Web.xml "ResourceRef_", when I checked web.xml there was no ID on the resource reference to copy across; and the JNDI Name "services/cache/instance_", as when I was setting up the resource in the server console the default name was of the form "jdbc/...". "services/..." sounds to me more like a "service tier" EJB reference, and in fact the Type dropdown contains "common:EJBLocalRef" & "common:EJBRemoteRef" which seem more appropriate to the Ejb Reference Bindings than the Resource Reference ones. So I added an Ejb Reference Binding, just to see what that looked like. The Name "EjbReferenceBinding_1204815208266" was interesting - how come that one added the (presumably unique) numeric reference to the end, when the Resource Reference Binding didn't? The JNDI Name, however, was also "EjbReferenceBinding_1204815208266" which seems strange. I was expecting something like "services/cache/..." again, or maybe "ejb/someBeanHome"; I'd be very surprised if the JNDI name WAS used for the Home interface when deploying a bean was of the form "xxxBinding_nnn". Having said that, since I don't have any EJBs involved in the nbproject, perhaps I shouldn't read too much into the values it used for those.
Reproducible in NetBeans IDE Dev (Build 200901120201). The default values are still the same.