Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/JPA/Basic JPA Development/Configuration/JPA/Defaults"
< EclipseLink | UserGuide | JPA | Basic JPA Development | Configuration
m |
m |
||
| Line 1: | Line 1: | ||
| + | {{EclipseLink_UserGuide}} | ||
=Defaults= | =Defaults= | ||
Each annotation has a default value (consult the JPA specification for defaults). A persistence engine defines defaults that apply to the majority of applications. You only need to supply values when you want to override the default value. Therefore, having to supply a configuration value is not a requirement, but the exception to the rule. This is known as ''configuration by exception''. | Each annotation has a default value (consult the JPA specification for defaults). A persistence engine defines defaults that apply to the majority of applications. You only need to supply values when you want to override the default value. Therefore, having to supply a configuration value is not a requirement, but the exception to the rule. This is known as ''configuration by exception''. | ||
| − | + | {{EclipseLink_Note | |
| − | + | |note=You should be familiar with the defaults to be able to change the behavior when necessary. }} | |
{{EclipseLink_JPA | {{EclipseLink_JPA | ||
Revision as of 13:33, 18 June 2010
Defaults
Each annotation has a default value (consult the JPA specification for defaults). A persistence engine defines defaults that apply to the majority of applications. You only need to supply values when you want to override the default value. Therefore, having to supply a configuration value is not a requirement, but the exception to the rule. This is known as configuration by exception.
Note: You should be familiar with the defaults to be able to change the behavior when necessary.
