ObjectDB Database Search

1-50 of 71 results

Programatic configuration or configuration file loaded from classpath or file

Programatic configuration or configuration file loaded from classpath or file

JPA Class Enhancer

the CLASSPATH - path to class or jar file(s), *? wildcards supported include: -cp : path to input user ... .Manager You can also specify the names of classes that can be located on the classpath by using ... .Enhancer -pu my-pu The -cp option can be used to specify an alternative classpath (the default

Dependency from enhanced classes to the objectDB library

.osgi.internal.loader. classpath .ClasspathManager.defineClass(ClasspathManager.java:632) at org.eclipse.osgi.internal.loader. classpath .ClasspathManager.findClassImpl(ClasspathManager.java:588) at org.eclipse.osgi.internal.loader. classpath .ClasspathManager.findLocalClassImpl(ClasspathManager.java:540

Failing in embedded mode, correct javax.persistance?

Hansson Knut Hansson It seems to be a classpath issue. Try the following: Download the last ObjectDB version. Include objectdb.jar from that zip file in your classpath . Remove any other JPA / ObjectDB jar files from the classpath . Alternatively, include in the classpath only objectdb-jee.jar + 

Cannot cast com.objectdb.jpa.Provider to PersistenceProvider

project. objectdb.jar is added into GF's classpath (domains\domain1\lib\ext folder). Any help ... This is what I get when I put objectdb-jee.jar in GF's classpath . Mention: I have just objectdb-jee.jar into the classpath . SEVERE:   java.lang.NoClassDefFoundError: javax/persistence/spi

disabling JDO in objectdb embedded mode

/PrimitiveValue.jdo"). I don't have such file on my classpath . So my question is: how can I prevent objectdb ... Support Hi, On my classpath I have  the entry PrimitiveValue.class. For many entity classes, I ... of the classpath is dumped for each single exception. I even don't see a trace that is related to ObjectDB

com.objectdb.o.InternalException: java.lang.NoClassDefFoundError: java/sql/Date

.   esharris Earl S Harris You will have to add ObjectDB to the classpath rather than as a module, as ... . Your example works fine in Eclipse if ObjectDB is added to the classpath : (Mickey Mouse, Disney ... the compiler back to 1.8, deleted module-info.java, and put objectdb on the classpath , the application

Compare old and new schema

the classpath ) and view the content of the old database with the old schema. support Support Thanks ... about the data stored in the database when entity classes are not in the classpath ? If I can reproduce ... without entity classes in the classpath but the metamodel is empty. How does your explorer get to metamodel

AttachNotSupportedException

to the classpath , but that did not make any difference. What am I doing wrong? Best regards, Rui RuiRosado Rui ... and had no problem at all. BTW: we included the path to \objectdb\bin in the CLASSPATH environment variable ... at our datacenter. After reinstalling and resetting the classpath this message did not appear

Apache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found)

Tomee's classpath ) nor other parts, excepting the following persistence.xml: com.objectdb.jpa.Provider ... to use JTA. You may try removing objectdb.jar from TomEE classpath , and putting it in the web ... . It seemed that actually I was putting objectdb.jar in the classpath in a wrong way. Now I use common.loader

createQuery method error

my classpath . can anybody help? thanks   hongsun Hong Sun Maybe you have an old JPA or ObjectDB JAR in your classpath before the new objectdb.jar file. What version of ObjectDB are you using?   support Support Thanks. I got it.  I have javaee-api-5.jar in my classpath which causes the error hongsun Hong Sun

Corrupted Database or error in ObjectDBExplorer?

) available in the the classpath (either in the Explorer or using your application) in order to update ... and then opening the database with the modified class available in the classpath . Removing that temporary ... the classpath .  This may fix the database. Please check and update. support Support Hello, the work

javax.persistence.PersistenceException: No Persistence provider for EntityManager named in Karaf 4.0.7 and OSGi DS test

Neon.1, Bndtools 3.3.0). In order to build the code, you need to have lombok in the classpath (https ... an appropriate JPA implementation in the classpath . You must make sure that ObjectDB is available in

DB Explorer and Doctor unable to open DB file

with a classpath that includes access to all your classes. In that case the synthetic class generation mechanism will not be needed. support Support The workaround with the changed classpath for Doctor

WebSphere Liberty Configuration

located? in the web application? On the server classpath ? Do you have other JPA implementations in the classpath ? If you have other error messages (from other configurations) please post them. support

Error occured during initialization of boot layer

is currently not supported as a module so you will have to add it to the classpath . See your project ... -modular (delete module-info) and included the objectdb.jar in the classpath . The program works now. Thanks for the help :) Sweetwater Marc

enhancement issue

file you need to: Have the JAR file in the classpath that is available to ObjectDB. Sometimes setting ... you have to make sure that the path is included in the application classpath before the jar file

Failed to enhance dynamic type

available in the classpath during enhancement? When a class is missing, ObjectDB Enhancer tries ... parameter. it is not supposed to be in the classpath at that moment and I am curious

Modifying something with Explorer -> app JPQL with Enum doesn't work anymore

is running the Explorer with your classes in the classpath . It may make a difference and serve as ... the classpath , the Explorer uses the schema as defined in the odb file). Please try to remember

ObjectDB License Error I got

+ ObjectDB on the classpath classpath = sourceSets.main.runtimeClasspath mainClass = 'com.objectdb.Enhancer

Unable to persist TreeMap

the Explorer with your classes available in the classpath . support Support Build 2.5.1_02 should fix most cases. Adding the classes to the Explorer classpath may still be needed in some cases. support Support

Embedding ObjectDB on server application

the classpath (i.e. JPA is available but not ObjectDB). It could also happen if the path ... like a classpath issue. Maybe objectdb.jar is available only in compilation and not at runtime

Problem Using Reflection

that these classes are available to ObjectDB in the ordinary application classpath or the thread context classpath , so no synthetic classes are generated. support Support Thanks.  I'll investigate further. mwarble M. Warble

Running doctor.jar with entity classes in classhpath

with model.jar (my entity classes in it) in classpath but it doesn't work (new entities still dont show up in ... a workaround, you can follow these 2 steps: Run the Explorer with the new class in the classpath :  

alter table

and the new class is available in the classpath , but this is indeed a step that has to be done. Alternatively, I think that you may run the Doctor specifying a classpath that contains the new class. BTW

Is there an administration tool with which I could create extra indexes?

class in the classpath in order to update the schema. Run the ObjectDB Doctor (in repair mode) to build the new index. Step 2 may be skipped if you run the Doctor (step 3) with your up to date classes in the classpath . support Support

mapping file is not being loaded

directory). Both objectdb.jar and objectdb-jee.jar are on the classpath . Finally, the application

Enhancer failure: Failed to process class file of type

; main = 'com.objectdb.Enhancer'   classpath = sourceSets.main.runtimeClasspath   args '-cp

Java 8 Enhancer Problem

Hello! I am currently migrating my project to Java 8. I'm using Spring and AspectJ load time weaving. Unluckily the LTW option of Spring is global. If it's enabled it also tries to find other class transformers on the classpath . This is normaly not a problem because the ObjectDB enhancer ignores

Low performance when getting grove roots

classes on my classpath even if I do not need them (if I use Hibernate, for example

Explorer in 2.3

your own static methods you have to run the Explorer with classpath that contains your classes

javax.persistence.PersistenceException

to the plugin runtime classpath . Fixing  "SELECT p FROM Point p" to  "SELECT p FROM Pilot p

OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011)

to get such messages unless ObjectDB cannot find your entity classes in the classpath . When an entity

Mismatch client-server protocol prefix

version 2.6.2. Also there's only one objectdb jar on the classpath . It's also not a network problem

Type xxx is not found (error 301)

your classpath before objectdb.jar - this happens for example if you use old Glassfish version that contains JPA 1.0. support Support

EntityManager getMetamodel() causes crash

.MyEntity      true Otherwise, ObjectDB may search and register all the entity classes in the classpath . support Support

Adding indexes on existing entities.

the classpath . Update: Starting ObjectDB 2.6.6 new indexes are automatically built and activated in

Finance data from SQL Server into ObjectDB daily

up to carry this out. Just make sure you have all dependencies in classpath and make sure

UserException: Package com.example.model is not found by the enhancer

for enhancement and when these classes are available in the classpath . This method is used in

Conditional Selection

also on the server side (by running the server with the correct classpath ). support Support Interesting solutions

Single Server License and Embedded Mode

don't need to define the .odb in a specific location or include any additional jars in the classpath

Connect to objectdb database

may indicate that the persistence.xml file is not found by JPA/ObjectDB in the expected path in the classpath

Method not found on...

) must be available for the server in its classpath . support Support

Access objectdb.conf as class loader resource

with your configuration resource before objectdb.jar in the classpath . support Support

Schema-Update: Deactivation of automatic entity class removing and introduction of a new class remove in the schema config

exist in the classpath ? btc_es BTC EmbeddedSystems ObjectDB doesn't currently support removing ... itself was still available in the classpath . If we complete remove the class, it works as we hoped.   ... :28) btc_es BTC EmbeddedSystems If a class is not available in the classpath but needed by ObjectDB

Feature suggestion: auto-detection of entities via persistence.xml extension

file. The classpath root that contains the persistence.xml file and any jar file specified with jar-file  in the persistence.xml file (but not the entire classpath ) are searched for annotated

Errors after unexpected server shutdown

the classpath )  in which that index is not defined, and then again redefine the index by accessing the database with a class (in the classpath ) in which that index is defined. Alternatively

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

is not anywhere in the classpath . You are not using classes that have been enhanced by an older

Error reading UTF string (Serialized Objects in Explorer)

- does it work? If it works, you may try running the Explorer with a classpath that contains

Inverse OneToMany Mapping and EmbeddedId

.xml file in the classpath 13:32:52.560 [main] DEBUG org.hibernate.jpa.HibernatePersistenceProvider