Hi

 

I noticed the discussions about the problems with marshalling Hibernate
proxy objects with Castor.

I have the same problem.

I have defined my POJOs as lazy (proxy) in Hibernate.

When Castor tries to marshal them, I would get exceptions (SQLexceptions in
combination with Castor XML field handler implementation classes).

 

I decided to to make sure that all fields were supplied with the set-method
attribute of castor. I also set the class attribute auto-complete to false
to prevent Castor from introspecting the objects.

 

But it did not work. 

In order to go around this problem, I had to change my Hibernate class
mappings. I disabled lazy/proying on the classes.

But of course nrate  Castor from introspecting the objects.

, now I have a serious performance issue.

 

I wondering: “Has this problem alreadya serious performance issue.

 been solved in CASTOR 1.1 ?  (I am using version 1.0.5 of CASTOR.)

 

Kind Regards

Urso Wieske

 

 


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.7/712 - Release Date: 6-3-2007
15:42
 

Reply via email to