[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] GFv3 + EclipseLink >=2.1.1: Remote EJB client cannot transfer JPA entities through remote session bean

We provide a feature that allows you to selectively load parts of the object. That is a fetch group. If you are not using this feature explicitly, you will not have any issues with disabling it.

The most likely reason you see this problem is for some reason the classes are weaved on one side, but not on the other. This feature weaves in an instance variable that will have to be serialized and deserialized, if that instance variable is unknown on either the sender or the receiver, that will likely cause marshalling issues.

What is the application you are serializing from? A JPA application running on glassfish? A standalone JPA application? How do you get your entity manager?

What about the application you are serializing too? (same questions)

-Tom

Xavier Callejas wrote:
Tom,

You are a genious!

This is the one that workaround the problem:

eclipselink.weaving.fetchgroups=false

What means that option disabled?

I made my tests with Glassfish 3.1 m7 witch includes EclipseLink 2.2.0.v20101020-r8375, I supose it should be the same with GFv3.0.1+EclipseLink 3.0.1.

Regards,
Xavier.