On Aug 10, 2007, at 10:03 AM, Peter Karich wrote:
I get heavy memory problems in my calculations, while doing the
following procedure 100,000 times: I create a meeting, calculate
sth. and remove it. Cayenne forces me to register all the
'meetings' and will reference them although I don't
ay be wrong but from my reading, I seem to recall that JPA supports
> > unregistered objects, so JPA may be able to help you here. I think
> > JPA also supports non-persisted objects in the class hierarchy, so you
> > might even be able to define a TemporaryMeeting subclass (or
>
Mike Kienenberger schrieb:
I may be wrong but from my reading, I seem to recall that JPA supports
unregistered objects, so JPA may be able to help you here. I think
JPA also supports non-persisted objects in the class hierarchy, so you
might even be able to define a TemporaryMeeting subclass
I may be wrong but from my reading, I seem to recall that JPA supports
unregistered objects, so JPA may be able to help you here. I think
JPA also supports non-persisted objects in the class hierarchy, so you
might even be able to define a TemporaryMeeting subclass (or
superclass) of Meeting
Hallo,
as discussed here [1] and there [2].
I am seeking for a solution where the following works:
Room r = new Room();
getContext().registerNewObject(r);
Meeting m = new Meeting();
r.addMeeting(m); //[3]
I get heavy memory problems in my calculations, while doing the
following procedure 100
