5 | ObjectDB Overview. Suitable for database files ranging from kilobytes to terabytes. Supports both Client-Server mode |
5 | Database Management SettingsThe <database> configuration element specifies back end (database engine) settings that are relevant on the server side and in embedded mode. The default configuration file contains the following <database> element: <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery |
5 | Obtaining a JPA Database Connection or a socket to a remote server) in a connection pool and use them to speed up future EntityManager |
5 | Database Doctor engine (not using one server process), thus bypassing ObjectDB internal file lock protection |
5 | Auto Generated Values. To minimize round trips to the database server, IDs are allocated in groups. The number of IDs in each |
1 | Step 1: Create a Java EE Web ProjectWe start by creating a new Java EE 6 Web Application project in NetBeans: Open the [New Project] dialog box, e.g. by using File > New Project... Select Java Web > Web Application and click Next. Choose a Project Name (e.g. Guestbook) and click Next. Select GlassFish Server 3 (or above) and Java EE |
1 | JPA Web App Tutorial - NetBeans Project Run > Run Main Project... (or F6). Choose or define the server and click OK. If a browser is not opened - open it at http://localhost:8080/Guestbook/. |
1 | Step 6: Run the Web Application. You can stop the Tomcat server and open the database file in ObjectDB Explorer: This is the end |
1 | Step 3: Add a Context Listener Class. The database will be closed when the web application stops (or when the web server shuts down), by |
1 | Step 3: Create an ObjectDB Data Source). Specify an ObjectDB connection url - either embedded (e.g. c:\points.odb) or client-server (e.g |
