Chapter 2. Configuration

2.1. Introduction
2.2. Runtime Configuration
2.3. Command Line Configuration
2.3.1. Code Formatting
2.4. Plugin Configuration
2.5. JDO Standard Properties
2.5.1. javax.jdo.PersistenceManagerFactoryClass
2.6. Kodo Properties
2.6.1. kodo.AggregateListeners
2.6.2. kodo.AutoClear
2.6.3. kodo.AutoDetach
2.6.4. kodo.BrokerFactory
2.6.5. kodo.BrokerImpl
2.6.6. kodo.ClassResolver
2.6.7. kodo.Compatibility
2.6.8. kodo.ConnectionDriverName
2.6.9. kodo.Connection2DriverName
2.6.10. kodo.ConnectionFactory
2.6.11. kodo.ConnectionFactory2
2.6.12. kodo.ConnectionFactoryName
2.6.13. kodo.ConnectionFactory2Name
2.6.14. kodo.ConnectionFactoryMode
2.6.15. kodo.ConnectionFactoryProperties
2.6.16. kodo.ConnectionFactory2Properties
2.6.17. kodo.ConnectionPassword
2.6.18. kodo.Connection2Password
2.6.19. kodo.ConnectionProperties
2.6.20. kodo.Connection2Properties
2.6.21. kodo.ConnectionURL
2.6.22. kodo.Connection2URL
2.6.23. kodo.ConnectionUserName
2.6.24. kodo.Connection2UserName
2.6.25. kodo.ConnectionRetainMode
2.6.26. kodo.DataCache
2.6.27. kodo.DataCacheManager
2.6.28. kodo.DataCacheTimeout
2.6.29. kodo.DetachState
2.6.30. kodo.DynamicDataStructs
2.6.31. kodo.ExecutionContextNameProvider
2.6.32. kodo.FetchBatchSize
2.6.33. kodo.FetchGroups
2.6.34. kodo.FilterListeners
2.6.35. kodo.FlushBeforeQueries
2.6.36. kodo.Id
2.6.37. kodo.IgnoreChanges
2.6.38. kodo.InverseManager
2.6.39. kodo.JMX
2.6.40. kodo.LockManager
2.6.41. kodo.LockTimeout
2.6.42. kodo.Log
2.6.43. kodo.ManagedRuntime
2.6.44. kodo.Mapping
2.6.45. kodo.MaxFetchDepth
2.6.46. kodo.MetaDataFactory
2.6.47. kodo.MetaDataRepository
2.6.48. kodo.Multithreaded
2.6.49. kodo.Optimistic
2.6.50. kodo.OrphanedKeyAction
2.6.51. kodo.NontransactionalRead
2.6.52. kodo.NontransactionalWrite
2.6.53. kodo.PersistenceServer
2.6.54. kodo.Profiling
2.6.55. kodo.ProxyManager
2.6.56. kodo.QueryCache
2.6.57. kodo.QueryCompilationCache
2.6.58. kodo.ReadLockLevel
2.6.59. kodo.RemoteCommitProvider
2.6.60. kodo.RestoreState
2.6.61. kodo.RetainState
2.6.62. kodo.RetryClassRegistration
2.6.63. kodo.SavepointManager
2.6.64. kodo.Sequence
2.6.65. kodo.TransactionMode
2.6.66. kodo.WriteLockLevel
2.7. Kodo JDBC Properties
2.7.1. kodo.jdbc.ConnectionDecorators
2.7.2. kodo.jdbc.DBDictionary
2.7.3. kodo.jdbc.DriverDataSource
2.7.4. kodo.jdbc.EagerFetchMode
2.7.5. kodo.jdbc.FetchDirection
2.7.6. kodo.jdbc.JDBCListeners
2.7.7. kodo.jdbc.LRSSize
2.7.8. kodo.jdbc.MappingDefaults
2.7.9. kodo.jdbc.MappingFactory
2.7.10. kodo.jdbc.ResultSetType
2.7.11. kodo.jdbc.Schema
2.7.12. kodo.jdbc.SchemaFactory
2.7.13. kodo.jdbc.Schemas
2.7.14. kodo.jdbc.SQLFactory
2.7.15. kodo.jdbc.SubclassFetchMode
2.7.16. kodo.jdbc.SynchronizeMappings
2.7.17. kodo.jdbc.TransactionIsolation
2.7.18. kodo.jdbc.UpdateManager

2.1. Introduction

This chapter describes the Kodo configuration framework. It concludes with descriptions of all the configuration properties recognized by Kodo. You may want to browse these properties now, but it is not necessary. Most of them will be referenced later in the documentation as we explain the various features they apply to.

Kodo JPA/JDO supports both JPA and JDO configuration styles. JPA utilizes the XML format described in Section 6.1, “persistence.xml” of the JPA Overview. JDO uses standard Java properties files. Specify your Kodo configuration options in the format native to the specification you are working with. If you are working with both JPA and JDO in the same application, use the configuration format of the specification you use most. JPA and JDO have different standard settings for many properties - for example, JPA looks for entity metadata in annotations, while JDO looks for metadata in .jdo files. The format of your configuration files determines Kodo's default values for these specification-dependent settings.

[Note]Note

You can explicitly declare specification-dependent settings such that a JDO properties file configures Kodo for JPA defaults, or an JPA XML file configures Kodo for JDO defaults. However, it is more robust to use the configuration format native to the desired specification.

 

Skip navigation bar   Back to Top