Note that DataContext creation is cheap. What I typically do in situations like
this is to periodically create a new data context that you can throw away. When
it's gone, the associated objects will be gc'ed. Eg: you could periodically
dump the "reading" data context and create a fresh one after
I have a server application that continually reads data from sensors. At
set intervals the data is summarized. This summary data is used to create
Cayenne data objects of type Reading. A short transaction commits these
Reading objects to the database, after which it is not important that they
are h
So what do your pojos (entity classes) look like? Like andrus said,
typically these have a specific implementation for cayenne. If you just
have plain fields with fetters and setters then you will need some custom
logic to make cayenne work with them.
For creating the model you need to do new Da
On 8 Dec 2011 at 16:18, Andrus Adamchik wrote:
>
> In the custom module define DataDomain loading services to
> reverse-engineer the POJOs instead of loading mapping from XML. This
> is the biggest task, requiring some understanding of Cayenne APIs.
> Feel free to ask here if you get stuck with a
On Sat Dec 10 16:39:50 2011, Andrus Adamchik wrote:
Could be a bug (in Derby?). Probably worth opening a bug report at
https://issues.apache.org/jira/browse/CAY ... Also would be helpful if you
could take a thread dump when the app is frozen to see what the app is doing at
this moment. IIRC we
