Internal Website Search

51-60 of 200 resultsRefresh

Database Explorer

-89c5b299d865/image.png"> Running the Explorer file. You can run it from the command line as follows: > ... a path to it has to be specified. Alternatively, you can run the Explorer by double

Database Transaction Replayer

might be slow if the database is large. Running the ObjectDB Replayer The ObjectDB Replayer tool is bundled in the objectdb.jar file. It can be run from ... > The Replayer can also be run up to a specified transaction, e.g.: > java

Java EE 6 JPA Tutorial - IntelliJ Project

To open and run the Java EE 6 Web Application ... ). Define Run Configuration: Select Run > Edit Configurations Run the project in IntelliJ IDEA: Select the new run

Spring MVC JPA Tutorial - NetBeans Project

To open and run the Spring MVC JPA tutorial ... Project. Run the project: Select Run > Run Main Project... (or ... > Note: To run the application on GlassFish - change the transaction type from RESOURCE_LOCAL

JPA Web App Tutorial - NetBeans Project

To open and run the JPA Web Application tutorial ... >guestbook-web directory and click Open Project. Run the project: Select Run > Run Main Project... (or F6). Choose or define the server and click

Java EE 6 JPA Tutorial - Eclipse Project

To open and run the Java EE 6 Web Application tutorial ... ;Finish. Run the project in Eclipse: Right click the project node and select Run As > Run On Server. (this command

[ODB1] Chapter 1 - About ObjectDB

>ObjectDB is written entirely in Java. Therefore, it can run on any environment that supports Java ... other platform), simply by taking the ObjectDB and JDO jar files with you. You can even run your application ... > In client-server mode, an ObjectDB server is running on a separate JVM (in a separate process

[ODB1] Chapter 6 - Persistent Objects

of other classes are referred to as persistence aware. Persistence aware classes must also be run ... persistent fields is also reachable. On every run of the garbage collector, all the unreachable objects ... of the database garbage collector requires an explicit call. It can be run in the Database Explorer, as

[ODB1] Chapter 3 - Persistent Classes

>The classic method to enhance classes is to run the enhancer from the command line. First ... .jar:/objectdb/lib/jdo.jar The enhancer can be run without arguments to get usage ... for the classes (the default is the classpath in which the enhancer is running):

[ODB1] Chapter 5 - JDO Connections

> has to be specified. In this case, a database server is expected to be running on a machine named running on localhost (the same machine) and listening to the default port ... can be used during the entire application run. This may be a good option in a single-user desktop