Hi,

I have Java code with Hibernate mapping files to map to a db2 database, the application runs fine within Websphere 5.0 (i.e using IBM JRE 1.3 ) but when i switch to a Sun JRE 1.3.1_01 the same app does not work, it gives a No Persister for : java.lang.Long or some other such errors, in short it is not able to talk to the database.

I am using Hibernate 2.0.3. I tried rebuilding Hibernate with Sun's JRE and including the hibernate2.jar built, but this makes no difference.

There is a related problem i have noticed : If there are two Setter functions for a complex property, hibernate gets confused between the two methods using Sun's JRE but does not if i use IBM JRE.

example :
class Container
{
getContent( ) returns a Content object,
setContent( Content a ) and setContent( SubContent name ),
}
with the mapping file pointing to a Many to one Content class.
Then when i run with Sun's jre, i get a SEVERE exception saying :
SEVERE = Expected type : SubContent, actual value : Content.

I think the JRE is called the second setContent() function for some reason.
Would appreciate any help in how i can resolve this, or information if you have seen the JRE mismatch problem before,

Thanks.

This usually happens if your exception handling idiom is wrong! ie. you swallow an exception and keep working with the session.

Hi,
I have caught the exception at the first point it occurs and am not reusing the session, i get it at a call to save() or saveOrUpdate().
If it were a mapping problem, it should happen when i use IBM's JRE also, should i move to the 2.1beta5 version of Hibernate.
Thanks.

I don't believe you, but if you can reproduce it in a VERY simple main() method, submit it to JIRA and i will take a look.

Hi Gavin,
I was able to recreate it, i have posted the problem on JIRA for Hibernate 2.0, would appreciate your help,
Thanks.

Hi Gavin,
I have tried both your methods, which are
1) remove overloaded get/set methods or
2) move to 2.1 Hibernate and use access="field"
but i get the same exception in both. I have sent the set of code in a zip file to gavin@hibernate.org, can you take a look.
Thanks,

please don't email me stuff! This is what JIRA is for.

Hi Gavin,
The getFormula/setFormula method was overloaded for Sun's JRE with a isFormula()/isAggregation() method which caused the problem. By renaming the isXXX() methods, i got rid of the problem,
Thanks,