Home » Search

About quick start

71-80 of 200Refresh
Forum
1

Query problem after transaction commit

> Test_Connection: connected 03> UI: start query [query for all object Goods successfully] 04> SELECT u ... 07> UI: start printing result 08> code= A, desc= Good A, byUser= test 09> code= B, desc= Good B ... created [create Goods D successfully] 13> UI: start query [query for all Goods D successfully] 14
Forum
1

100% CPU when using multiple BETWEEN

in the class, but not relevant to the problem.   A query like this causes the java process to start ... to be present in 2.5.1_04. Thank you very much for your quick response on this issue. Best regards Emil prolancer
Forum
1

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

.StandardContext.startInternal(StandardContext.java:5179) at org.apache.catalina.util.LifecycleBase.start ... of objectdb.jar. Thanks for such a quick reply. That's one of the main reasons I love ObjectDB
Forum
1

Database size is much larger than expected (x2)

. In many cases (not always) a user can isolate the problem quite easily by starting from the failed ... didn't work. You can report a problem with no test case of course - but don't expect a quick fix in
Forum
1

EntityManager JPA or JDO impl and different behavior

we use spring to start everything. If I do: System.out.println("EntityManager Name: " + em.getClass ... this case. Hi, Thanks for the quick investigation. That has indeed fixed that issue
Forum
1

Guestbook example from tutorial does not work.

to try running the Maven version of this tutorial. Thank you for your quick reply. But thats a maven ... -repository for this?     You are right, this requires a better solution. Starting build 2.6.2_02
Forum
1

Homepage and forum nearly inaccessible

, and it has been like that for 1 year, since I started using ObjectDB. I'm also accessing from Europe ... for your quick fix, which is what we all now expect from you, as normal. :) We think we found two issues
Issue
1

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

. No problem. Build 2.2.6_01 included a dirty and quick fix that used get as a prefix for both get and set ... well. Starting build 2.6.4_03 Enhancer generated hidden methods will have a __odbHidden_ prefix
Forum
1

Performance problem

without your entity classes (which we do not have) results in a quick response time of about 100ms for each ... is unavailable. You found that the problem starts with result #53. If you run the query in the Explorer
Issue
1

query.getResultList() throws ClassCastException

of instantiating entity objects. Make sure your classes are enhanced. Thanks for the quick turn around, I'll try out 2.3.1. In regards to the tips: Yes I noticed this when I started pushing things into