RE: CFMetaDataParser hiding exception info

2006-10-13 Thread Patrick Linskey
It sounds like you didn't recompile your sources between Kodo 4.0 and Kodo 4.1. Kodo 4.0 used different package names than Kodo 4.1, and our backwards compatibility efforts didn't include binary-compatibility. (Sorry about the Kodo spam, btw.) -Patrick -- Patrick Linskey BEA Systems, Inc.

RE: CFMetaDataParser hiding exception info

2006-10-13 Thread Roytman, Alex
Patrick, As far as kodo.jdo.ProxyMap I fixed it (I had some custom proxies which implement it) My point was that you at least should log an exception if you hide it or it is virtually impossible to figure out why the class could not be loaded. Or better yet differentiate handle only

JDO Query on interfaces Kodo 3.4 style do not work in Kodo 4.1

2006-10-13 Thread Roytman, Alex
If Kodo 4.1 is used with 3.4 developed applications, it does not allow queries on interfaces any more essentially making it impossible to transition 3.4 application without full conversion to JDO2. I wonder if it is not possible to emulate JDO2 persistent interfaces behavior from introspecting