ObjectDB ObjectDB

Internal Website Search

81-90 of 200 resultsRefresh

objectdb:2.8.4 - Error occurred during initialization of boot layer

:/Projects/Anritsu/Perforce/ws_alexander.golyshkin_ALL/DEV/RTD_7_6_0_JAVA_UPDATE_JDK9/JavaApps ... .jar;D:\Projects\Anritsu\Perforce\ws_alexander.golyshkin_ALL\DEV\RTD_7_6_0_JAVA_UPDATE_JDK9\JavaApps\out\test\RTDEngine;D:\Projects\Anritsu\Perforce\ws_alexander.golyshkin_ALL\DEV\RTD_7_6_0_JAVA_UPDATE

Running JPA Queries

that to only print the country names, a query using projection and retrieving country names directly

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

-B.tgz To reproduce the problem described below, simply download the test project, open in NetBeans8 ... -2.6.9_01. In the test case, only a single Project entity is used, and 2 project objects ... the building of 2 separate - usually large and complex - Projects, via the @Stateful ExtProjectBuilder

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

. It is marked knowingly as CRITICAL by me because it makes the ObjectDB system unusable for a real project ... it, which is just as bad. I attach a running project illustrating the problem, as well as screenshots. When the project runs it logs creation of objects. Please note that there are 2 Project objects, and note

After using the enhancer, Lazy loaded collections are no longer loading. They are set as null

, CascadeType.PERSIST}, mappedBy="account", fetch = FetchType.LAZY) @JoinColumn(name = "project_id", unique=true, nullable=false, updatable=false) protected List<Project> projects = new ArrayList<>(); public List<Project> getProjects() { return projects; } public void

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

($i,"element",e); log_info($i,"element.project",e.getProject()); List ... =TestDeepValues][project=TEST: project 1][id=45][name=TEST: test deep values]) INFO: ConfigBean []: testQuery: element.project([class=Project][id=1][name=TEST: project 1]) INFO: ConfigBean []: testQuery

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

.greensoft.objectdb.test.entity.Permissions com.greensoft.objectdb.test.entity.Project com ... createProject(EntityManagerFactory emf) { format().outHeader2("Create Project and Element model ..."); Project project = new Project(null, "project"); //NB: Project has no project

Step 6: Run the Web Application

You can run the application now by right clicking the GuestServlet node (in the [Project Explorer] window) and selecting Run As > Run on Server > Finish: Since we are using ObjectDB in embedded mode - the database file is created under the Tomcat directory. You can stop the Tomcat server and open

Step 2: Define a JPA Entity Class

To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the project node (in the [Package Explorer] window) and selecting New > Class. Enter guest as the package name - use exactly that case sensitive package

[ODB1] Chapter 3 - Persistent Classes

(and also from the command line) is to add a new simple main class to a project that applies on the fly

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support