|
| Re: Strange serialization behavior [message #893076 is a reply to message #893069] |
Mon, 02 July 2012 13:43  |
 Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Sebastien,
EObjectImpl isn't marked serializeable, so I assume its fields aren't
being serialized. You'd need to implement specialized read/write logic
in your derived implementation classes...
On 02/07/2012 3:24 PM, Sebastian Sprenger wrote:
> Hallo,
>
> I needed to pass an EObject for a RMI. Therefore I had to nake my
> generated model classes implement java.io.Serializable. I managed that
> by creating a root interface called SerializableEObject extending
> EObject and Serializable. All my model Interfaces extend
> SerializableEObject. So far so good, I was able to pass the Objects.
>
> Now comes the strange part:
> My passed Object has a Containment Reference. Before passing the
> EObject the eContainer()-Method return the desired container Object.
> After the EObject is the eContainer-Reference is null. Is there a way
> to circumvent that?
>
> Thanks for any help, Sebastian
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03444 seconds
] 
Search
Help
Register
Login
Home
