About setup

11-20 of 49Refresh
Forum
2

Source not found error after downloading ObjectDB 2.3.7_04

.   For setup I downloaded the ObjectDB zip file. Placed it in source code of my existing project. I added ... found error. Please tell me if I am doing correct setup. ObjectDB is not open source so the source
Forum
2

Spring 2.5 LocalContainerEntityManagerFactoryBean, no getSharedCacheMode()

I'm trying to setup Spring + JPA + ObjectDb in my test environment and having trouble with the following:
Forum
2

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

setup: - The diagnostics here have been recorded carefully at every step, including Git tracking ... .java:2130) at com.objectdb.o.UMR$ac.i(UMR.java:1368) ... 23 more Remarks on configuration and setup
Forum
1

Apparent Lazy Loading issues.

(this is what the unit test is setup testing at the mo). To reproduce the error, try replacing
Forum
1

BIRT plugin: Trouble with Client/Server connection

:6136) Nothing made it to the log. The following is my setup: Dev Versions:     MyEclipse Enterprise
Forum
1

Compile time enhancement using build.xml of a Netbeans web application

/kb/74/java/project-setup.html#building-compile-on-save). However, I have figured
Forum
1

Configuration and Activation Code in ObjectDB 2.x

for the reply. I setup the configuration and updated the objectdb.conf with the activation code
Forum
1

Connecting to a remote objectdb server

I am trying to configure my application in a client-server objectdb setup via tcp/ip. So I first made sure that the remote objectdb server is running using telnet from my local.  $ telnet db.mydomain.com 6136 (worked fine, is able to connect...) My db was configured below:
Forum
1

Criteria query error: Unexpected query token

the simplicity of objectdb. Now I'm going to setup the JDO annotations to build up indexes.  
Forum
1

EntityManager JPA or JDO impl and different behavior

when they are changed (this is what the unit test is setup testing at the mo). To reproduce the error, try