Internal Website Search
1-50 of 200 resultsPosting Sample Code To demonstrate a technical question or an issue - you may have to provide a complete runnable sample program . If an unexpected exception (e.g. NullPointerException or ClassCastException ) is thrown by ObjectDB - posting the full stack trace with no sample program (using the Issue Tracking | |
How prevent post-compile enhancement of non entity classes I have recently moved to post - compile enhancement (from automatic run-time enhancement) using ... under clearly named packages: But the following for per-file post - compile enhancement also invokes ... and per-file compilation (with NetBeans " compile on save" off), but it is not yet perfect at only invoking | |
Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity extends Element { On post - compile enhancement I get this error (as reported in the odb log file ... script for the post - compile enhancement the class path is: javac.classpath:lib/objectdb.jar:/usr ... comment out that static LOGGER variable init line, the error vanishes and post - compile enhancement | |
Post-compilation enhancement vs Automatic Run-time enhancement We are getting massively different results on field loading between explicit post - compile ... on the fly runtime enhancement is applied only to entity classes, where post compilation ... of is now provided under forum posting : Pre-detach loading: retrieval by navigation not working in | |
JPA Class Enhancer ObjectDB Enhancer is a post compilation tool that improves performance by modifying the byte code of compiled classes after compilation . Enhancement is mainly for user-defined persistable classes ... defines a Java compiler plugin that includes enhancement: ... ...   | |
Compile time enhancement using build.xml of a Netbeans web application of empty targets to override in build.xml, such as - post - compile and - post - compile -single. I ... to have a version of this that works with - post - compile -single acting on single files (incremental compilation ... . webel Dr Darren Kelly I wrote: I want to have a version of this that works with - post - compile | |
Maven driven compile time ehnancement classes during compile time. Just add the following to your pom.xml:   ... ; compile compile   | |
Concerning coding style of the example in the posting instructions with reference to the coding example in the posting instructions and many of your other examples posted in ... . Firstly, the posting instructions state: 'Use a single Java file with one main class + static ... for entities, compliant entity classes belong in separate files. Secondly, in many forum posting examples | |
Can't post on your forum Since yesterday, I can't post on the forum because it always says that I should log in in order ... post on the forum. I tried removing the cookies, but nothing. I tried in another browser, but the same. I have new bugs to post , so it's pretty important. zmirc Mircea Chirac We used your account | |
finding post-persist pre-commit objects Hi, I'm wondering if there is a way to have post -persisted, pre-committed, objects show up in queries? ie: the object has been persisted, but not yet committed. Dave dmoshal David Moshal Yes, by setting the flush mode . support Support thanks, worked for me. dmoshal David Moshal | |
Bug when posting threads with Firefox 34.0.5Bug when posting threads with Firefox 34.0.5 | |
ObjectDB JDBC to Object compiler Hello , some products developed by JDBC , So we cannot use ObjectDB. My idea is , you can make JDBC To ObjectDB wizard compiler or something like this. You can eliminate JDBC Requests from Java Code. It can be Intellij or Eclipse IDE plugin for ObjectDB. It dedects strings and combinations | |
Does run time enhancer due to GlassFish/Payara do anything that would affect loaded compile-time entity classes ? do anything that would affect loaded compile -time enhanced entity classes (other than just logging, typically just | |
Compiled Queries and Cache objectdb.conf has options for query results and program cache. (objectdb.conf database query-cache results and programs, https://www.objectdb.com/java/jpa/setting/database#The_query-cache_element_ .) query. compile (); query.closeAll(); After code like above, are the query results | |
Issue with compile time enhancementIssue with compile time enhancement | |
Query Parameters in JPA execution, because it eliminates the need for repeated query compilations . Named Parameters (:name ... its own query compilation , which is very inefficient. On the other hand, when using parameters, even if a new ... with the same query string and use a cached compiled query program , if available. Secondly | |
Post-compile enhancement sometimes causes error in generic loops: incompatible types found: java.lang.Object: required: Entity I have moved from automatic run-time enhancement to explicit post - compile enhancement in an Ant build.xml in a NetBeans web app, and sometimes on editing a file that performs a generic for loop over an @entity type I get a generics error. The generic for loop is: for (Steel s | |
Database Management Settings of running queries. The programs attribute specifies how many compiled query programs should be cached. Cached query programs may eliminate the need to compile queries again but the queries | |
Pre-detach loading: retrieval by navigation not working in if statement that older one: Post - compilation enhancement vs Automatic Run-time enhancement , where support ... here : Automatic on the fly runtime enhancement is applied only to entity classes, where post compilation ... a reflective JSF view). The issue I reported (otherwise addressed by post - compile Ant task | |
Apache License, Version 2.0, January 2004 to compiled object code, generated documentation, and conversions to other media types. "Work" shall | |
Literals in JPQL and Criteria Queries are more generic and efficient because they can be compiled once and then run many times with different | |
Running JPA Queries to cast the above results to a parameterized type ( List ) will cause a compilation warning | |
JPA Criteria API Queries of using the criteria API is that errors can be detected earlier, during compilation | |
Database Explorer on the query window. If the query compilation fails, an error is displayed in the query window | |
Privacy Policy Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy ... to this Privacy Policy are effective when they are posted on this page. Your Rights ... about this Privacy Policy, You can contact us by visiting this page on our website: https://www.objectdb.com/ post /new?op=new | |
General Performance Issues Illustrated with a Specific Method that. Please refer to my first post on https://www.objectdb.com/forum/2857 for details. MOH-SL ... in the future if you follow the posting instruction and post minimal examples (for example ... , would have been eliminated). Unfortunately all your posts today violate the posting rules and if you want to continue to use | |
Exception on creation when running multithreaded; for the CDI I can see 3 queries: [2011-08-09 01:51:47 #37 query. compiler ] [2011-08-09 01:51:47 #38 query. compiler ] :1:notNull]))" eval="4.3054" var="1" prm="0" reg="1" :1:notNull])" eval="3.0043" var="1" prm="0" reg="1" variable="$$owner" / [2011-08-09 01:51:47 #39 query. compiler ] :1:notNull | |
Dependency from enhanced classes to the objectDB library; setContextClassLoader , as suggested in post #4 in that thread before working with ObjectDB ... Support Hello, in the example of post #3, we get a different error message than in post #1. I had not described in post #3 clear enough. The other message is because we have referenced the ObjectDB | |
Step 1: Create a Maven Web Project 1.6.10 org.apache.maven.plugins maven- compiler -plugin 1.7 1.7 org.codehaus.mojo exec-maven-plugin 1 ... -plugin 6.1.10 10 foo 9999 start-jetty pre-integration-test run 0 true stop-jetty post -integration-test | |
Step 1: Create a Maven Web Project; org.apache.maven.plugins maven- compiler -plugin   ... ; stop-jetty post -integration-test | |
objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation the Ant build). - The NetBeans project for the console app uses a post - compile , pre-deployment Ant ... according to the Clean and Build time and Ant script post - compile enhancement. They are not affected ... the following forum postings and issue reports (but please do not visit them from here now, the diagnostics | |
Possible cause for "Enhancement of type ... is old and cannot be used" am using post - compile , pre-deployment enhancement using an Ant script, and I have taken extra care to make ... . the Ant post - compile , pre-deployment enhancement task has run and reported the enhancements): Type com ... that uses property access mode. More details are in this issue thread (see post #4). support Support | |
Error 990... and then new version? I was about to post (here, since the provided url is restricted), I noticed there was a new release ... version does not seem to be in that repository... or at least I can't get my compiler ... , dangit! Of course as soon as I post , I finally find the bottom of your very out-dated maven | |
Object as parameter results in exception the primary key is used as a literal, which means that the query has to be compiled every time ... . So ObjectDB would indeed cache this query the way it is? Please ignore my original post - the literals ... will be coded as Criteria queries. Willks William Your original post is of a great value | |
Gradle-Kotlin Code Contributions if someone has a Tutorial build.gradle.kts file and would post a copy. Second, I thought it might be valuable to have a thread where people could post and find Gradle-Kotlin code potentially useful to ObjectDB ... in that it lacks a task to enhance the compiled classes. Deprecated Gradle features incompatible | |
JPQL JOIN FETCH Error;OutOfMemoryError and the query compilation error in action? support Support The OutOfMemoryError ... variables per query. The query compilation error may be related to missing schema ... which you are more than welcome to take a shot at. The select statement from post #2 above causes the  | |
[ODB1] Chapter 3 - Persistent Classes. 3.3 JDO Enhancement The ObjectDB JDO Enhancer is a post compilation tool that modifies the byte code of compiled classes. Classes to be enhanced must be located in class files and not in | |
[ODB1] Chapter 7 - JDOQL Queries. The execute() method compiles and runs the query. If there is no age field in class Person or ... . If the query compilation succeeds, the Extent of Person instances in the database is iterated object by ... (for future JDO extensions), so casting is required. Compilation and execution of queries | |
PersistenceManager.newQuery(compiled) - JDO Method JDO Method in javax.jdo.PersistenceManager Query newQuery ( Object compiled ) Create a new Query using elements from another Query . The other Query must have been created by ... , except for the candidate Collection or Extent . Parameters: compiled - another Query from the same JDO implementation Return: the new Query Since: JDO 1.0 | |
Query.compile() - JDO Method JDO Method in javax.jdo.Query void compile () Verify the elements of the query and provide a hint to the query to prepare and optimize an execution plan. Since: JDO 1.0 | |
ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection. There is an Ant script with post - compile enhancement of all entity classes. When you clean and build ... Unpack, open in NetBeans8.1, and then perform Build. There is an Ant script with post - compile ... . [EDIT: solved at https://www.objectdb.com/forum/1928 ] Also, although I am using post - compile | |
[ODB1] Chapter 9 - ObjectDB Explorer are displayed on the query form. If the query compilation fails, an error is displayed on the query form ... create and compile the classes externally in your IDE, and then use the "File | Load New Classes" menu | |
[ODB1] Chapter 5 - JDO Connections the compiler does not force a throws declaration if code that uses JDO is not wrapped by a try-catch ... , such as IOException , is forced by the compiler ). Therefore, extra caution is required by | |
Explorer bug ? Objects seem to be missing from database in Class view, but are present as references) INFO: RequestBean []: Created: com.greensoft.entity.test.TestBlock [null](TEST: « compiled » test block) INFO: RequestBean []: Persisted: com.greensoft.entity.test.TestBlock [65](TEST: « compiled » test ... : RequestBean []: Updated: com.greensoft.entity.test.TestBlock [65](TEST: « compiled » test block) INFO | |
[ODB1] Chapter 2 - A Quick Tour. Because JDOException is a subclass of RuntimeException , the compiler does not enforce the throws declaration | |
After using the enhancer, Lazy loaded collections are no longer loading. They are set as null; Note: This scenario was working until running the enhancer on compiled jpa entities timbob1000 Tim Osborn Your issue cannot be reproduced, since the posted code is not runnable. Particularly the invocation of find in your code does not compile . The following code included an attempt | |
ObjectDB enhancement fails on "is" form for @Transient boolean isLoaded(), ok for "getter" form @Transient boolean getLoaded()) { this.loaded = loaded; } No matter whether using javaagent run-time enhancement or post - compile enhancement ... (an no matter whether using compile -on-save or not) I get at run-time this error (and for every subclass | |
javax.jdo.Query NoSuchElementException to next() . Since: JDO 1.0 void compile () Verify the elements of the query ... operators = , += , etc. and pre- and post -increment and -decrement are not supported | |
javax.jdo.PersistenceManager: the new Query Since: JDO 1.0 Query newQuery (Object compiled ) Create a new Query using ... Extent . Parameters: compiled - another Query from the same JDO implementation Return: the new Query | |
javax.jdo.FetchGroup the factory method. Return: the name Since: JDO 2.2 boolean getPostLoad () Get the post -load property of this FetchGroup. Return: the post -load property Since: JDO 2.2 int getRecursionDepth (String  ... ;postLoad) Set the post -load property of this FetchGroup. Return: the FetchGroup Throws |