This feature can be enabled/disable per project basis from the Properties window. Right-click on the project, select “Properties”, choose “Run” categories and select/unselect the checkbox “Deploy on Save” to enable/disable this feature.
In NetBeans IDE, expand “Configuration Files”, edit “persistence.xml” and replace:
<properties/>
with
<properties>
<property name="eclipselink.logging.level" value="FINE" />
</properties>
In the “Services” tab, right-click on “GlassFish Server 3.1”. All the commands to start, stop, and restart are available from the pop-up menu. The server log can be viewed by clicking on “View Server Log” and web-based administration console can be seen by clicking on “View Admin Console”.
- Find the location of database in “Services” tab of NetBeans, right-clicking on “JavaDB”. The default location is .netbeans-derby in your home directory. Close NetBeans and delete this directory.
- Remove .netbeans directory in your home directory.
- Start NetBeans and the database will be recreated and new records will deployed into Sample database.
In “Services” tab of NetBeans, expand “Servers”, choose the GlassFish node, and select “View Domain Server Log”.
The GlassFish output window may be showing the following log message:
keepstate is true and will not create new auto timers during deployment.
This can be fixed if you right-click on the project and select “Deploy”, right-click again now select “Run”.
This may happen if the namespace prefix was manually specified during the composite component creation. In this case you need to add the following namespace prefix mapping to the .xhtml document:
xmlns:ez="http://java.sun.com/jsf/composite/ezcomp"
Right-click on “org.glassfish.samples” package, select “New”, “Java Class...”, specify the name as “ApplicationConfig”. Change the generated source code to:
@javax.ws.rs.ApplicationPath("webresources")
public class ApplicationConfig extends javax.ws.rs.core.Application {
}