Internal Website Search

.objectdb.o._LockTimeoutException: Write lock cannot be granted for a.b.c.d.EE#150. irrespective if I set ... setting a shared lock in the EJB could get around this, but this would be global and impact all threads ... on stale updates. Willks William Support of pessimistic lock timeout  setting ( javax.persistence

to the schema as expected, however their type is set to unknown - we were expecting Boolean. The attached ... ) is set to unknown. Both are defined as Boolean in Java code. As a result, update operations ... like the following fail to change the value from null to false: UPDATE RecordingMetaData AS r SET r

.conf file. I am using JDO and setting the persistenceManager as follow properties.setProperty("javax ... , how can i set the temp directory using my java class  e.g  setting through  ... directory where fileName.odb is located. But i want to set the tempority folder location

(attached to forum thread mentioned above), I set  Database max-threads.  In the documentation, it was not completely clear to me if this setting controlled how many internal threads ObjectDB uses, or if ObjectDB is doing some sort of queue/locking whose depth is determined by this setting

a variable (private Set cellHeldCharacters;) which holds the IDs of the characters within the cell ... is it illegal/unrecommended to do it for a Set ? For a better picture, I have: @Entity public class Character ... ;   private double cellSize;     private Set cellHeldCharacters

, mappedBy="parent") private Set abstractContainers = com.google.common.collect. Sets ... of com.google.common.collect. Sets $SetFromMap - field xxx.AbstractContainer.abstractContainers at com ... Vladimir Tsichevski Maybe the set contains objects that cannot be serialized. Check the full stack trace

. ie. Set terms;     // the set is filled with SearchTerm objects ...   any term should be simpler: Set terms; // the set is filled with SearchTerm objects

. But exporting large binary data sets is very slow. To avoid memory problems the binary data type is read step ... data sets the way is slow. We have an own entity for storing binary data (pictures, documents). Hint ... , which will retrieve only objects with larger primary key as the next set of objects. Usually the problem

already. ObjectDB seems to clear some fields that are @ElementCollection Set of my objects ... is emptied, but not null. So, my @ElementCollection Set fields become empty sometimes during development ... it. Initially, I was not using @ElementCollection on my Set fields from User class. I've seen

of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service ... Cookies for the purposes set out below: Essential Cookies These are Session Cookies,  ... is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data

and specifies their specific settings (username, password, permissions, quota). The default configuration ... . A superuser is authorized to manage server settings using the ObjectDB Explorer . A value of "$default" for the username attribute indicates a virtual master user definition. All the settings of that master

The configuration element specifies Secure Sockets Layer (SSL) settings for secure communication ... has to be installed on the server machine. Setting the Configuration     To use SSL the enabled attribute of the ssl  element has to be set to true . Every Keystore / Truststore file

The configuration element specifies settings for running an ObjectDB Server . The server is affected also by other elements in the configuration file, particularly the and the configuration elements ... its subdirectories can be accessed by the server. Appropriate file system permissions have to be set

an instance of Address , which is another entity class. Due to the CascadeType.DETACH setting ... setting , when an Employee instance is merged the operation is automatically cascaded

FROM ... [WHERE ...] UPDATE ... SET ... [WHERE ...] Besides a few exceptions, JPQL is case insensitive ... . Organization of this Section This section contains the following pages: Detailed explanations on how to set

) in the persistent object model are represented by the following sets of interfaces and enum types ... in the above sets extend the Bindable interface, which may be used in defining criteria query

Persistence fields can either be accessed by JPA directly (as fields) or indirectly (as properties and get/ set methods). JPA 2 provides an annotation and an enum for setting the access mode: More details are provided in chapter 2 of the ObjectDB manual.

Criteria Queries The CriteriaQuery interface provides methods for setting the ORDER BY clause ... (c. get ("population"))); Unlike other methods for setting criteria query clauses - the orderBy

on a different physical device by setting the path attribute in the configuration . The recording

, MEMBER, MIN, MOD, NEW, NOT, NULL, NULLIF, OBJECT, OF, OR, ORDER, OUTER, POSITION, SELECT, SET , SIZE

The way a field of a persistable class is managed by JPA can be set by the following annotations: Additional annotations (and enum) are designated for enum fields: Other additional annotations (and enum) are designated for date and calendar fields: Chapter 2 of the ObjectDB manual explains how to use all the above annotations.

describing some tools and settings that are specific to ObjectDB:

instances to zero: int count = em. createQuery ("UPDATE Country SET area = 0"). executeUpdate

The JPA Criteria API interfaces in this group are used for setting the SELECT and ORDER BY clauses and for representing query results as tuples. SELECT Clause Elements The content of the SELECT clause in a criteria query is represented by Selection : Because Selection  is a super interface

directory can be specified by setting the target parameter before executing the backup query:  

JPA defines three types of persistable classes which are set by the following annotations: Chapter 2 of the ObjectDB manual explains these annotations in detail. Entity and mapped super classes can be further configured by annotations that specify cache preferences and lifecycle event listener

A JPA Persistence Unit is a logical grouping of user defined persistable classes (entity classes, embeddable classes and mapped superclasses) with related settings . Defining a persistence unit is optional when using ObjectDB, but required by JPA. persistence.xml Persistence units are defined in

The interfaces in this group are in use for setting a criteria query FROM clause. Criteria Query Variables The FROM clause  in JPA queries (as in SQL) defines the query variables. Query variables are represented in criteria queries by descendant interfaces of the From interface: Range

to set numeric value of field property com.greensoft.objectdb.test.entity.Element.id using reflection ... " [ObjectDB 2.6.9] javax.persistence.RollbackException Failed to commit transaction: Failed to set numeric ... : com.objectdb.o.UserException: Failed to set numeric value of field property com.greensoft.objectdb

. set (platformConnector); } ... } I get an exception thrown  when trying to create an entity ... ._PersistenceException: Failed to locate set method for field property domain.PlatformTicker.platformConnector using ... ObjectDB's. However the error message Failed to locate set method for field property... is misleading

that have already signed (which are retrieved from the request's guestDao attribute that is set by the controller in the previous step). The next step (and the last in this tutorial) is setting the Spring XML configuration .

the request's  guestDao attribute that is set by the controller in the previous step). The next step (and the last in this tutorial) is setting the  Spring XML configuration .

+ ")"; } } The Guest entity class will represents guests in the database. We also need to configure JPA by setting

; copy and paste to replace its content with the following settings : 4.0.0 com.objectdb.tutorial

qualified class name is set (you may use copy & paste). Click the Finish button to create

file and use copy and paste to replace its content with the following settings : 4.0.0 com.objectdb

JPA persistence unit (with default settings ) was generated in a persistence.xml file that was added

that have already signed (which are retrieved from the request's "guests" attribute that is set by the servlet in

of the ObjectDB data source. The next step is using this data source to create a data set for the BIRT report.

by setting a  META-INF/persistence.xml file: Right click the src/main/resources node (in

these fields for content assistant) and click Next . In the [Format Chart] tab you can set the chart title

JPA persistence unit (with default settings ) was generated in a persistence.xml file that was added

that have already signed (which are retrieved from the request's "guests" attribute that is set by the servlet in

from the request's "guests" attribute that is set by the servlet in the previous step). The next step

" attribute that is set by the servlet in the previous step). The next step (and the last one in this tutorial) is running the web application .

cls, String filter) In the first form, the candidate class is automatically set to the class of the specified candidate Extent , and in the second form, the candidate collection is automatically set ... : Calendar calendar = Calendar.getInstance(); calendar.clear(); calendar. set (2000, 0, 1); Date date

JDO supports two modes of persistable classes that can be set by the following annotations: Non persistable classes that should be enhanced (because of accessing persistent fields of other classes directly) can be marked with: The identity mode of persistence capable classes can be specified by using:

The way a field of a persistable class is managed by JDO can be set by the following annotations and enum types:

demonstrated above. The Index Rebuilder Tool Setting indexes for a new class that does not have persistent

be configured. If the ConnectionFactory property is set (non- null ) then all other Connection properties including ConnectionFactoryName are ignored; otherwise, if ConnectionFactoryName is set (non- null ... is set (non- null ) then ConnectionFactory2Name is ignored. Operational state ( PersistenceManager