5 | Future JDO versions?We are about to release our first product using ObjectDB (as a small embedded store), and soon hope to release a much larger product using ObjectDB (will need an OEM license). What really interests us is JDO. We have been using JDO for over a decade and have found it consistently a far better API |
5 | JSON serialization and __odbHidden membersHi.. Building a REST API (Jersey-based one) I noticed that every object I serialize to JSON has a clone field with "__odbHidden" suffix, e.g.there's "id" and "id__odbHidden" is also (unwantenly) present with the same value. In general, we can annotate fields to include/exclude them from JSON |
5 | UserException: Package com.example.model is not found by the enhancer. The most user-friendly, environment-friendly option seems to be via the enhancement API. Is there a way that I |
5 | ObjectDB and JPA API + extensions. ObjectDB supports also JDO. But in the JPA context Hibernate and ObjectDB |
5 | Optimistic lock failed/database/forum/41 The RollbackException wraps the real exception - see: http://www.objectdb.com/api |
5 | Access ClassTransformerHello, As in our OSGI Environment, we do need to manually weave classes. To be able to do so, we'd need access to the ClassTransformer from ObjectDB. However, there's only the global enhancer api which is not of any help. There's the JEhancerAgent which seems to implement a ClassTransformer as |
5 | Failed to synchronize replicated database. if the slave was down). support Support So there is not currently an API that would allow us to cleanup old |
5 | Recommendation - concurrent access multiple class vHi! I've just started to architect a new system, stateless JSON API, which is expected to have very high load and to require more servers for parallel deployments (same app across multiple servers). I am considering using ObjectDB, because of its advantages and easy usage, but I'm afraid |
5 | EntityManager JPA or JDO impl and different behavior://www.objectdb.com/api/java/jpa/OneToMany state: "When the collection is a java.util.Map, the cascade |
1 | Better OSGI CompabilityWe are currently using objectdb using osgi. However, the objectdb jar seems to be very monolithic and should be more modular to make it easier to use it with osgi, samples are: - Remove SWING dependency from core objectdb bundle - Externalize persistence and jdo apis and not putting them into |
