I am seeing something, that I am sure I just don't understand right.

I have an ACCOUNT which has a relationship of one to many ADDRESSES. All this runs in a WebService. I exposed two methods: GetAddresses and AddAddress. Both take an account ID. So I fetch the account and return the associated addresses. When I need to add an address I simply fetch an account, then create a new address. I don't update Account.Addresses, just save the object.

The problem is that I don't get the updated list back on the next query to GetAddresses (the new address is not there).

So what's the right way of doing this? Do I need to update the list all the time or set some parameters on the relationships?

Thx
dB.

Could you post the mapping file?
Also, can u post the part of the code that adds the address & saves the object?

That would help in analyzing...

If save of new address completes successfully (think you have already checked it in the database) then there could be two reasons:
1. Your account object along with associated collection of addresses is cached in the session cache.
2. Collection of addresses for your account is cached in the second-level cache.

In first case it should be enough to evict account after you add an address.

In second - you can evict addresses collection from second-level cache (using SessionFactory.EvictCollection method).

But it would be much simpler if you will just add address to the collection and save whole account object.

It doesn't seem to quite work. The problem is accross sessions. This is an ASP.NET application (and I am keeping the session within the HTTP context). A second session doesn't see the results until a few seconds - clear problem in caching.

Am I doing something wrong or is this by design? Should I be flushing the second level cache for all the sessions to be updated?

I fount my problem. I was forgetting to close the hibernate session at the end of the request.

Thanks to all!