Abstract
Configuring a persistence application involves specifying the bits of information, additional to the code, that the execution environment or persistence platform may require in order for the code to function as a runtime application. Packaging means putting all the pieces together in a way that makes sense and can be correctly interpreted and used by the infrastructure when the application is deployed into an application server or run in a stand-alone JVM. Deployment is the process of getting the application into an execution environment and running it.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Metadata is the default input, so if metadata is the desired input, it does not need to be specified. If scripts are the desired inputs, then the create-script-source or drop-script-source properties could be specified without the need to specify either the create-source or drop-source.
- 2.
The exception to this rule may be the optional element of the mapping annotations, which may result in a NON NULL constraint, but which may also be used in memory to indicate that the value is or isn’t allowed to be set to null.
- 3.
The resulting column must be supported by the provider runtime to enable reading from and writing to the column.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2013 Mike Keith
About this chapter
Cite this chapter
Keith, M., Schincariol, M. (2013). Packaging and Deployment. In: Pro JPA 2. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4927-6_14
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4927-6_14
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-4926-9
Online ISBN: 978-1-4302-4927-6
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)