About JBoss AS

91-100 of 200Refresh
Manual
4

Database Server

embedded mode, ObjectDB is integrated as a library and runs within the application process, which is much more efficient. As a result, embedded mode should be preferred when possible. For example ... Server tool is bundled in the objectdb.jar file. You can run it from the command line as follows
Manual
4

DELETE Queries in JPA/JPQL

As explained in chapter 2, entity objects can be deleted from the database by: Retrieving ... a separate EntityManager for DELETE queries. As with any operation that modifies the database, DELETE ... variable DELETE FROM Country AS c  // AS + an optional variable ObjectDB supports using the java.lang
Manual
4

Online Backup

), since an ObjectDB database is stored as an ordinary file in the file system.  ObjectDB supports ... applications that provide round the clock service (24/7/365) such as most web applications. Starting Online ... directory location. Notice that if the target argument is specified as a java.io.File instance and em
Manual
4

Paths and Types in JPQL and Criteria API

as arguments. Path expressions that navigate from one object to another. Instances of user defined ... , however, is valid even if the persistent field is declared as private (which is usually the case). Navigation ... over all the Country objects in the database. For a country with no capital city, such as Nauru, c.capital
Tutorial
4

Step 7: Run the Spring Web App

the content of the index.jsp file (which serves as the default front page) with the following redirection to the controller path: If Tomcat 6.0 is installed as ... the [Project Explorer] window), selecting Run As > Run on Server, selecting the Tomcat 6.0 server
Manual
4

Storing JPA Entity Objects

or implicitly as a result of a cascade operation. Explicit Persist The following code stores ... .getTransaction().commit(); The Employee instance is constructed as an ordinary Java object and its initial ... of other persistable types can only be stored in the database embedded in containing entities (as
Manual
4

Schema Update

databases as a complementary operation to renaming or moving these elements in the IDE during source code refactoring. Only these schema changes are specified in the configuration file. As explained in ... " /> The hierarchy, as demonstrated above, is strict: elements
Manual
4

Literals in JPQL and Criteria Queries

Literals in JPQL, as in Java, represent constant values. JPQL supports various types of literals ... literals should be used sparingly as queries that use parameters instead of literals ... that comparison with NULL in JPQL follows the SQL rules for NULL comparison rather than the Java rules, as
JDO Doc
4

javax.jdo.JDOEntityManager

of interest. If the classes parameter is specified as null, events for all persistent classes and interfaces ... might flush instances as if flush were called, but it is not required to do so. If an optimistic ... . The Transaction instance supports options as well as transaction completion requests. Returns
JDO Doc
4

javax.jdo.PersistenceManager

is specified as null, events for all persistent classes and interfaces will be sent to listenerInstance ... the consistency of instances in the cache against the datastore. An implementation might flush instances as ... () request, the default values for options will be restored to their values as specified in