Internal Website Search

of a Netbeans web application project to specify ObjectDB compile time enhancement, for both single ... for Netbeans uploaded here would be very helpful. Until now I have been working with run- time enhancement ... enhancement and JRebel , as reported under:  JRebel integration feature , so I want to try compile time

about 10-12 seconds. If i remove ANY 5 left joins, query execution time drops to about 50 milliseconds. Adding a new left join on remaining 8 slows down query execution time drastically. Please help ... to, for exmple, 9 query execution time drops to about 60 milliseconds. Kind regards, Pero   Pero

It would be very useful if each entry in the log file has a date/ time stamp. Thanks, Carl   FastModel Ben Schreiber Version 2.2.2 adds date/ time stamps to the log. Thank you for your suggestion. support Support

during the time of issue: From our logs the issue seems to have occurred between 3:45 am to 4:15 am on Nov 22nd ... such long wait times ? CAPdev CAP Dev There are no known issues that may be related. How do you know

EntityManager.refresh takes a long time for entity object Person in this code:     logger.log(Level.INFO, "begin select for person " + new Date().toString());     ... only objects in his context? Operation time reaches 30 - 40 seconds. Please help to understand why. 

Maven-based compile- time enhancement applied to entity modules (only), so I know these checks ... load time ) ?     webel Dr Darren Kelly Please provide more information about these checks, such as log messages or stack traces. support Support

We detected that the first Persist() of an entity take much longer than all subsequent calls. We have a small example (see Appendix) which outputs the following times : First transaction with persist ... : Could you explain the long time for first persist? btc_es BTC EmbeddedSystems Some operations

timed out: connect NestedThrowables: java.net.ConnectException: Connection timed out: connect The same

We are getting massively different results on field loading between explicit post-compile enhancement and automatic run- time enhancement. Testing exactly where and when the results are different for our demo web app is a very time consuming task, and very difficult, it means testing literally 100s

I have an entity library which I have integrated build time enhancement in.  The enhancer reports it has processed all of my persistent classes.  When I attempt to run a Bootstrap process with this library I get the error shown below.  The entity referenced in the error (Terms

support these expressions (as an extension to JPA) - support of date/ time methods ( YEAR , MONTH

I get errors when trying to persist anything in java. time .* For example LocalDate, Month, Period. Will these be supported sometime in the future?   scoobyrooster Jason Java 8 date and tome is not supported yet, except by serialization (which is not recommended and disabled by default

around after searching google. However this exception only happen after running the app the second time . If I'm runnig the app the first time after rebooting my system. Everything is ok but after closing the app ... embedded mode the database cannot be accessed at the same time by more than one process. Make sure

ObjectDB current status of the BIRT plugin

Java 8 time API

))) that normally take around 10 seconds but sometimes several times a day take around 3-10 minutes

to avoid to again and again transfer this huge database, we are a bit under time pressure hgzwicker

. Indexing a large amount of data may take considerable processing time . The enabled attribute

for the first time ) is 1. For every transaction in which an entity object is modified its version number

is effective until terminated. The Customer may terminate the agreement at any time by simply

the specified schema updates every time a database is opened. When using client-server mode

an extension). For example: MOD(11, 3) is evaluated to 2 (3 goes into 11 three times with a remainder of 2

to change the terms and conditions, the products, services, prices, and programs mentioned in this site at any time , at its sole discretion.

with millions of objects in the database there is a huge difference in query execution time if proper

while at the same time sharing a single application-wide EntityManagerFactory . When the connection

entity class. This is done automatically in memory each time the entity object is loaded. The database

, but it is a one time operation. Once constructed, it can serve the entire application. Operations that modify

are listeners that should be applied by default to all the entity classes. Currently , default

is not in the current directory a path to it has to be specified. The tool's main class is com

is thrown. The exception is thrown either by persist (if that existing entity object is currently

ObjectDB requires Java 5 or later (Java 6 is preferred). As a pure Java application, ObjectDB should be able to run on any platform that supports the Java Standard Edition. Either the Java Development Kit (JDK) or the Java Runtime Environment (JRE) can be used. A version of ObjectDB for .NET is currently under development.

is not in the current directory a path to it has to be specified. The tool main class is com.objectdb

reference. In JPQL, the current FROM variable (or FROM tuple when there are multiple variables

. Only identification variables and path expressions are currently supported in the GROUP BY clause by all the JPA

;entity) Check if the instance is a managed entity instance belonging to the current persistence ... on an entity manager which has not been joined to the current transaction and a lock mode ... if invoked on an entity manager which has not been joined to the current transaction and a lock mode

() Create expression to return current date. Return: expression for current date Since: JPA 2.0 Expression currentTime () Create expression to return current time . Return: expression for current time Since: JPA 2.0 Expression currentTimestamp () Create expression to return current timestamp. Return

each time it is invoked. The isOpen method will return true on the returned instance. Return: entity ... time it is invoked. The isOpen method will return true on the returned instance. Parameters: map ... with the specified synchronization type. This method returns a new EntityManager instance each time it is invoked

You can run the application now by right clicking the Main node (in the [Projects] window) and selecting Run File . The expected output in the [Output] window, is: Total Points: 1000 Average X: 499.5 (0,0) (1,1) (2,2) (3,3) : : (998,998) (999,999) When you run the application for the first time

) When you run the application for the first time , a new ObjectDB database file is generated in the db sub

: mvn package jetty:run The current directory should be  guestbook-web (containing the  pom

the command line: mvn package The current directory should be  guestbook-jee6

The current directory should be points-console (containing the pom.xml file). No need to download

jetty:run The current directory should be  guestbook-spring (containing the  pom.xml file

in a very short time , because it is very easy to use. In fact, it is the easiest JDO implementation

. This method has no effect if the instance is already deleted in the current transaction. This method ... and manipulation outside of a JDO environment. When detaching instances, only fields in the current ... instances must either be in the default-fetch-group , or in the current custom FetchPlan. Parameters: pcs

- the field number currentValue - the current value of the field Return: the new value for the field ... field - the field number currentValue - the current value of the field Return: the new value ... instance field - the field number currentValue - the current value of the field Return: the new value

should be used for the current transaction, whether instances may hold values in the cache outside ... () Commit the current transaction. Throws: JDOUserException - if transactions are managed by ... data store locks until commit time . Return: the value of the Optimistic property. Since: JDO 1.0

within the current transaction. If the JDO identity is being changed in the transaction, this method returns the object id as of the beginning of the current transaction. Return: a copy of the ObjectId ... jdoGetObjectId if the identity of the instance has not changed in the current transaction. If the JDO

(before the first time getPersistenceManager is called). The classes parameter identifies ... until it is added to the current set via addFetchGroups . Parameters: cls - the class or interface ... () Get a modifiable Set containing a mutable copy of all currently active (in scope) fetch groups. The methods

, then the ObjectId returned is only valid within the current transaction. Parameters: pc ... resource "META-INF/jdoconfig.xml", using the current thread's context class loader to locate ... , using the current thread's context class loader to locate the PersistenceManagerFactory class