Hi,
I've just migrated my app to Hibernate3. The surprise was that all the good design I've been trying to keep using Hibernate2 seems to be gone.

Logically, and as said in chapter 20, it is not a good practice to lazy- initalize our objects because eveytime we do that , we end up fetching up the entire model. In my applicaction I invoke the business logic using one Session Bean, close Hibernate session, get my Entity Bean and the whole process seems to clean and tidy. Now - using Hibenate3, I have to go back and close the session or, as said in Chapter3, I need some kind of Servlet filter to take care of Hibernate session.

Faisal
UK,B'ham

You are very confused.

That is true... since I've started using Hibernate3

So, if you are unable to read the Migration Guide (and that much is clear from your confusion about lazy loading), stick to Hibernate 2.

It's mispelling ...not confusion - non-initalized instead of initalized

The question is not mainly on how lazy initalization work in Hibernate3 . My main point is that in Hibernate3 I am no longer allowed to seperate the business logic from the web tier using a session bean . Do I have to send the live session back to close it? or do I have to use Servlet filter to deal with that. None of these should work. "a servlet filter can be used ...
We recommend that a ThreadLocal " as the documentation suggest is ...nonsense ... these work when I am invoking a single action.

Nothing changed between H2 and H3. You are making up excuses.

Ok, since you will probably post another load of nonsense, here is the deal: Step away from the computer and write down an explanation of your problem that is understandable to other people. If you don't know enough English, use your native language and find someone to translate it for you. But please don't post anymore.

I'm new to Hibernate. Still with the experience of doing a few code samples what I understood is...

If you are using lazy initialization,

Objects can not be INITIALIZED out side the scope of session, but once initialized objects can be accessed out side the scope of session.


This is same in H2 and H3.

Please correct me if I'm wrong.

totally correct soorajam.

And jukcoder, I assume you *did* notice that H3 now has lazy as default opposed to H3 (as documented in the english migration guide).

so, the semantics have *not* changed between H2 and H3 - but some of the default values for configuration parameters has.