v3.2GA (RC also)

Has anyone hit a problem where they persist an entity that contains an @Enumerated enumeration in one session, load it back in another, and do an equality test (== and .equals(...)) that returns false.

I have an enumeration Choice { YES, NO }; and a class Opinion that contains

@Enumerated
Choice choice;

...when I compare it to what I _know_ it is, it gives me a false, so with the below snippet

Choice myChoice= Choice.YES;
log.debug("Testing to see if opinion choice " + op.getChoice() + " is " + myChoice);
if(op.getChoice() == myChoice) {
log.debug("The choices are equal");
}else{
if(log.isDebugEnabled()){
log.debug("The choices are not equal.");
log.debug("Supplied choice has hashcode " + myChoice.hashCode());
log.debug("Opinion choice has hashcode " + op.getChoice().hashCode());
}
}


I get the following output from the above logging code:

Testing to see if opinion choice YES is YES
The choices are not equal.
Supplied choice has hashcode 19756588
Opinion choice has hashcode 26890590

This is the same for == and .equals(...).

I'm sure I'm just doing something naff here....has anyone come across this before?

Cheers
Adam

I failed to mention that my hibernate code was in an ejb, and the call was coming remotely (RMI) from the web layer. Currently you can't pass enums over RMI and expect them to work properly.

It's being worked on by sun http://bugs.sun.com/bugdatabase/view_bu ... id=6277781

pretty big overlook on suns part....the network is the computer, look we have enums now too.....oh :(

nasty.
If you change the protocol that might work though