12 | Explorer in 2.3 data and Strings. After playing with it for a while, here is a list of additional features I'd love to have: 1. Export of selected data: a. Simple - Select a range of cells or a column header and copy ... for circular references) c. Binary - Select some objects, serialize the data to a binary file |
11 | Externalising persistence.xml properties in Glassfish? environment in Glassfish 3.1 - the environment already is set up with the Postgres jta-data-source ... .ObjectDbJPAMockProvider</provider> <jta-data-source>jdbc/jpaProviderMockPool</jta-data-source ... . That is the easiest solution. Another way might be by setting a system variable with the url |
2 | Detached Entity Objects setting, when an Employee instance is detached the operation is automatically cascaded to the referenced ... setting, when an Employee instance is merged the operation is automatically cascaded to the referenced |
2 | JPA Query Structure (JPQL / Criteria) FROM ... [WHERE ...] UPDATE ... SET ... [WHERE ...] Besides a few exceptions, JPQL is case ... on how to set criteria query clauses are provided as follows: Criteria SELECT (select, distinct |
2 | JPA Metamodel API) in the persistent object model are represented by the following sets of interfaces and enum types ... the above sets extend the Bindable interface, which may be used in defining criteria query variables in |
2 | JPA Annotations for Access ModesPersistence fields can either be accessed by JPA directly (as fields) or indirectly (as properties and get/set methods). JPA 2 provides an annotation and an enum for setting the access mode: More details are provided in chapter 2 of the ObjectDB manual. |
2 | ORDER BY clause (JPQL / Criteria API) methods for setting the ORDER BY clause. For example, the following JPQL query: SELECT c FROM ... "))); Unlike other methods for setting criteria query clauses - the orderBy method takes a variable number |
0 | Step 5: Add a JSP Page that have already signed (which are retrieved from the request's guestDao attribute that is set by the controller in the previous step). The next step (and the last in this tutorial) is setting the Spring XML configuration. |
0 | flush()Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active ... will set the current transaction's RollbackOnly flag (see Transaction.setRollbackOnly). Since: JDO 2.0 |
0 | flush()Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active ... will set the current transaction's RollbackOnly flag (see Transaction.setRollbackOnly). Since: JDO 2.0 |
