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.
Product Version: NetBeans IDE Dev (Build 201508310002) Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) When adding a GlassFish Resource (e.g. JDBC Resource) to a Web Project via "New File" wizard and there is no glassfish-resources.xml file yet, it is being created into the WEB-INF folder. When the project is deployed, the configuration isn't loaded to the server. When the configuration file is moved to the "Server Resources" folder (where it used to be generated in 8.0.2) it is loaded successfully.
What is the real problem actually? I have tested sample app (Entity classes from DB and JSF Pages from entity classes using freshly created DS). The app is deployed OK and works. The datasource is deployed and it is application scoped resource. ./asadmin list-applications --resources Is this about the server node item?
You're right, I tried again and it's mostly working. I must have messed up something in my test code, because i was receiving a server errors, that resources can't be located. I was looking up all kinds of resources from one class and it seemed to me that all of them were failing. The only one still actually failing is JavaMail Session Resource, which fails to register when in WEB-INF folder. (The resources list under server node is involved partially, because I was used to verifying the availability of resources there. So when I haven't seen them there after the errors, I assumed none of them were registered at all, instead of being application scoped.)
(In reply to Stepan Zebra from comment #2) > > The only one still actually failing is JavaMail Session Resource, which > fails to register when in WEB-INF folder. > Ok, my bad again, seems like using Run on the project isn't enough in every situation and Deploy needs to be called instead... Closing invalid. Sorry for false alarm.