Hi,

can i get null value instead of LazyInitializationException after closing session.

when iam using beanutils or betwixt apis iam getting LazyInitializationException.

i need to avoid that exception and should get a null value.

how can i do that...

thanks in advance...

bye...




Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.0

Mapping documents:generated with middlegenide

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

Supposing you want to avoind LazyInitializationException on


The best way to do this, imho, is to convert your class like this:



Then have hibernate maps to property somethingImpl instead of something. This is how i do when i want to add logic to getters/setter but i don't want this logic to be triggered by Hibernate persitence automatisms. As the property somethingImpl as private getters/setters, beanutils shouldn't try to access them i think.

Hi,

Thanks for your fine solution but with that solution i have to write two more methods for each attribute in all my bean classes.

Dont mind.

Is there any other way to avoid that exception.

Yes.

don't close/disconnect the Session until you have finished manipulating your datas (which seems to me quite obvious to do, don't close your session unless you are sure you won't require more datas)

what im doing is getting the object loaded from DB and closing the session.

after that im passing that object to the Betwixt API to write to xml(only loaded data i wanted).but that betwixt api is parsing through the object graph.there when it just accesses the object which is not loaded there exception coming.

i wanted a way to get that object out of the context of the Hibernate.

This solution ain't elegant, but you can travel your object graph and nullify uninitialized properties before passing the graph forward:

http://forum.hibernate.org/viewtopic.ph ... highlight=

Then i think you'll have to handle this on betwixt part. There is most proably a way to manager exceptions in this tool.

thanks garyrung....

still im not able to do it..

im not getting a way to traverse the entire object graph to nullify uninitialized variables.

see my problem..

in my sales order i have foriegnkey relation ship with customer and quotation.

in my salesorder class i have the objects of customer and quotation.

while im loading salesorder object only foriegnkeys are loading not the entire object.

i have to nullify the remaining fields in the Customer and Quoatation object.

problem is how to nullify all the fields in those objects.

Can't you just close/disconnect the session after your have created your xml? Hibernate is supposed to be used transparently. Am not sure inspecting your objects to know if they are loaded is a good design approach, as it mean adding lots of persistence related code in your presentation layer!

if i do xml creation before closing the session that will create long chain in the xml.
i just wanted to nullify those uninitialized which are unwanted into xml file.

I don't know the api you are using, can't you request this api to not go deeper than 2 levels, for example? Or to exclude some properties?

This looks quite beyond the scope of Hibernate and you are trying to use a side effect of Hibernate (fields may be uninitialized and session closed to force some Exceptions) to achieved your result. That mean if in the future the internal behaviour of Hibernate changes (imagine a future Hibernate version loading the first 3 elements of each set because someone discovers it improve performances) and you will might get a different XML :/

dear tchize,

there is no such provision to controle it traverse to particular depth.

but there is a provision to exclude some properties from accessing.

if we go thruogh this approach we need to hard code.

if that is the case i can easily nullify the properties directly because as a developer i know which is loaded and which is uninitialized.

but im searching for a way through which i can do get null values instead of getting LIE.

Interesting idea, if you don't find coupling your model to Hibernate. There must be another way! :)

Yes, the most obvious, don't close session until you are finished using your objects.
But as the question was "can i get null value instead of LazyInitializationException after closing session." ..... :)

[quote="tchize]"can i get null value instead of LazyInitializationException after closing session."[/quote]

Sure. Why not let POJOs be POJOs and set the model object property to null in a service or DAO class instead?