WO5.4: Bug serializing/deserializing EOAndQualifiers?

Tom Woteki <[email protected]>
Newsgroups gmane.comp.web.webobjects.devel
Message-ID <[email protected]>
Hi:
I believe there is a bug in the serialization/deserialization of  
EOAndQualifiers in WO5.4. I'm wondering if anyone else has observed  
this before I file a bug.

I am porting an application verbatim from WO5.3 on 10.4.10 to WO5.4  
on Leopard. The serialization code works perfectly in the WO5.3   
environment but I get a ClassCastException

	at com.webobjects.eocontrol.EOAndQualifier.readObject 
(EOAndQualifier.java:250)

when I perform the deserialization operation in 5.4/Leopard.

I am working with an EOAndQualifier that resembles this as a string:

	((loginName = 'foobar') and (loginCount = '0'))

Upon deserializing the previously serialized version of this I get  
the exception noted above. If I merely change the "and" to "or"  
everything works fine.

I can formulate a workaround to this to solve my problem, but of  
course this doesn't fix the root cause bug I believe is present.

Has anyone else seen this?

Regards,
Tom

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.