| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Application Development Guide |
Part I Development Tasks and Tools
1. Setting Up a Development Environment
Part II Developing Applications and Application Components
6. Using the Java Persistence API
Additional Database Properties
Primary Key Generation Defaults
Changing the Persistence Provider
Restrictions and Optimizations
Using @OrderBy with a Shared Session Cache
Using BLOB or CLOB Types with the Inet Oraxo JDBC Driver
Named Native Queries and JDBC Queries
7. Developing Web Applications
8. Using Enterprise JavaBeans Technology
9. Using Container-Managed Persistence
12. Developing Lifecycle Listeners
13. Developing OSGi-enabled Java EE Applications
Part III Using Services and APIs
14. Using the JDBC API for Database Access
15. Using the Transaction Service
16. Using the Java Naming and Directory Interface
One of the default persistence provider's properties that you can set in the persistence.xml file is eclipselink.logging.level. For example, setting the logging level to FINE or higher logs all SQL statements. For details about this property, see Using EclipseLink JPA Extensions for Logging.
You can also set the EclipseLink logging level globally in the GlassFish Server by setting a JVM option using the asadmin create-jvm-options command. For example:
asadmin create-jvm-options -Declipselink.logging.level=FINE
Setting the logging level to OFF disables EclipseLink logging. A logging level set in the persistence.xml file takes precedence over the global logging level.
|