[zatix]

So, a few days has been passed since your last post. Any news?

[sabaka]

Fixes are committed few hours ago, you can download next nightly build and you will have them.

[zatix]

Fixes are committed few hours ago, you can download next nightly build and you will have them.

So, was this really a bug?
Are you a developer from Isomorphic?

Anyway, am I allowed to take a look at the source code or is the server side code closed?

I appreciate your attention.

[Isomorphic]

Yes, Sabaka works with us.

Whether this is a bug or not is a grey area. The features we need to do efficient paging are not support by EclipseLink in the way that other JPA providers support them. Regardless, we just went ahead and worked around the gap in EclipseLink here.

[zatix]

Just made a test with the lastest nightly build and had the exactly same problem.
I already made a minimal simple project with just the example quoted (and nothing else).

I insist on an working example of JPA2DataSource with embeddedId, could you provide some? You must have done some to test the fix.

Thank you.

[sabaka]

I'm confused just as much as you are.
This looks like wrong dependencies. Is it possible that you have several isomorphic_jpa.jar files in your classpath and wrong one is being loaded in runtime? And please check what nightly you are using (ensure that you're getting the latest one).

If this doesn't work, please provide complete source code of sample project you've mentioned. And exact Smartclient version you are using.

Thanks.

[zatix]

Which version did you fixed the bug?
I tested with the latest 4.0d and worked, but we were talking about 3.1p (as I said at the first post).

[sabaka]

Oh, ok - my fault. I did not pay attention that you're working with 3.1p version. I've ported that fix to 3.1p just now, so you can wait for next nightly build and have the fix.