Thank you Pierre, you are a genius!!!
Infact I was storing the objects from the database in some variables in
Application.java (I really didn't remember this)
So, when the session terminates and the EC is disposed, the objects are
still visible, in the variables, but when I try to read them the
Are you holding onto an EO that was created within the default
editing context?
E.g. are you assigning the User or Currency objects to a variable
within your application class, or to a static variable?
Pierre
On 7 Dec 2006, at 18:45, Chuck Hill wrote:
On Dec 7, 2006, at 8:40 AM, Daniel
On Dec 7, 2006, at 8:40 AM, Daniele Corti wrote:
well, I'm quite sure that it's the same and that it's called
Session.terminate():
When I wrote the first code, I thought it would be better to forget
all the objects in the ec, to reinizialize the ec with the session
so in the Session.java
well, I'm quite sure that it's the same and that it's called
Session.terminate():
When I wrote the first code, I thought it would be better to forget all the
objects in the ec, to reinizialize the ec with the session so in the
Session.java I've overwritten public void terminate()
public void _cl
Daniele,
I don't believe that you are getting the same editing context. The
default editing context for a session is created and "owned" by the
session instance. What is more likely is that you are expecting to
get fresh data from the database because you have a new
EOEditingContext.
One of these things is true:
- you think it is the same EC, but it is not
- the session did not terminate
What makes you think it is the same EC?
Chuck
On Dec 7, 2006, at 8:09 AM, Daniele Corti wrote:
Hi all,
I'm a little cofused: in my app I use as editing context the
Session.defaul
Hi all,
I'm a little cofused: in my app I use as editing context the
Session.defaultEditingContext(), and I thought that when the session is
terminated automatically the ec would be disposed. well, today I've notice
that when the session timed out, and I reenter in the app, when the session
is
