7 | JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception> <resource-root path="objectdb-jee-2.4.0_04.jar"/> </resources> <dependencies ... .servlet.api" optional="true"/> </dependencies> </module> The pom.xml is modified accordingly |
7 | objectdb:2.8.4 - Error occurred during initialization of boot layer the objectdb-jee-2.8.4.jar with following dependencies javax.persistence.jar javax.transaction.jar ... as shown in attached dependency file. Harman Alexander Golyshkin Yes. This is the preferred way to go. support Support |
5 | ClassCastException of same object type to be able to change plugins depending on who uses the application. So the classes cannot be in the main |
5 | Jboss 6 persistence.xml startup error> and here is the error: 2011-04-04 18:35:23,098 ERROR [org.jboss.kernel.plugins.dependency |
5 | Objectdb recovery (the exact effect depends on too many factors, so it has to be checked with your specific application |
5 | Problem of query With an aggregate function depends on the type of the fields (nb1, nb2, ...). If the type of your fields is long (or Long |
5 | Connection performace after upgrade to objectdb 2. The problem is that in my software, customers needs to load a component that depends on many odb file |
5 | Is 2 level cache in use? and then check if it is cached. The L2 cache doesn't always improve performance. It depends |
1 | NullPointerException in __odbGetNumMember, it may be possible for some entity classes to be loaded before enhancement, depending on how exactly |
1 | combined index not usedcombined index not used |
