Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » Proxy Resolution Problem
Proxy Resolution Problem [message #660373] Fri, 18 March 2011 07:42 Go to next message
Markus Herrmannsdoerfer is currently offline Markus HerrmannsdoerferFriend
Messages: 50
Registered: July 2009
Member
Hi *,

I have the problem that proxies of single-valued references do not get
resolved, even though resolve proxies is true. As a result, migrations
specified in COPE/Edapt are not working. I debugged a lot and found the
following code snippet in EStructuralFeatureImpl:

2815 public static class
InternalSettingDelegateSingleEObjectResolvingUnsettable extends
InternalSettingDelegateSingleEObject
2816 {
2817 public
InternalSettingDelegateSingleEObjectResolvingUnsettable(ECla ss eClass,
EStructuralFeature feature)
2818 {
2819 super(eClass, feature);
2820 }
2821
2822 @Override
2823 protected boolean isUnsettable()
2824 {
2825 return true;
2826 }
2827 }

Must the class InternalSettingDelegateSingleEObjectResolvingUnsettable
not inherit from InternalSettingDelegateSingleEObjectResolving instead
of InternalSettingDelegateSingleEObject? It seems to me that this only
affects reflective deserialization.
Thanks and cheers,

Markus
Re: Proxy Resolution Problem [message #660379 is a reply to message #660373] Fri, 18 March 2011 08:21 Go to previous messageGo to next message
Markus Herrmannsdoerfer is currently offline Markus HerrmannsdoerferFriend
Messages: 50
Registered: July 2009
Member
Unfortunately, I cannot switch to the trunk version of EMF in some
projects. Is there a way to circumvent this problem, i.e. to force these
proxies to resolve?
Thanks.

Am 18.03.2011 08:42, schrieb Markus Herrmannsdoerfer:
> Hi *,
>
> I have the problem that proxies of single-valued references do not get
> resolved, even though resolve proxies is true. As a result, migrations
> specified in COPE/Edapt are not working. I debugged a lot and found the
> following code snippet in EStructuralFeatureImpl:
>
> 2815 public static class
> InternalSettingDelegateSingleEObjectResolvingUnsettable extends
> InternalSettingDelegateSingleEObject
> 2816 {
> 2817 public
> InternalSettingDelegateSingleEObjectResolvingUnsettable(ECla ss eClass,
> EStructuralFeature feature)
> 2818 {
> 2819 super(eClass, feature);
> 2820 }
> 2821
> 2822 @Override
> 2823 protected boolean isUnsettable()
> 2824 {
> 2825 return true;
> 2826 }
> 2827 }
>
> Must the class InternalSettingDelegateSingleEObjectResolvingUnsettable
> not inherit from InternalSettingDelegateSingleEObjectResolving instead
> of InternalSettingDelegateSingleEObject? It seems to me that this only
> affects reflective deserialization.
> Thanks and cheers,
>
> Markus
Re: Proxy Resolution Problem [message #660454 is a reply to message #660379] Fri, 18 March 2011 13:41 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 30559
Registered: July 2009
Senior Member
Markus,

Yes, that looks wrong. Please open a bugzilla.

EStructuralFeature.Internal.setSettingDelegate can be used to set your
own setting delegate implementation into the feature that's not working
properly otherwise.


Markus Herrmannsdoerfer wrote:
> Unfortunately, I cannot switch to the trunk version of EMF in some
> projects. Is there a way to circumvent this problem, i.e. to force
> these proxies to resolve?
> Thanks.
>
> Am 18.03.2011 08:42, schrieb Markus Herrmannsdoerfer:
>> Hi *,
>>
>> I have the problem that proxies of single-valued references do not get
>> resolved, even though resolve proxies is true. As a result, migrations
>> specified in COPE/Edapt are not working. I debugged a lot and found the
>> following code snippet in EStructuralFeatureImpl:
>>
>> 2815 public static class
>> InternalSettingDelegateSingleEObjectResolvingUnsettable extends
>> InternalSettingDelegateSingleEObject
>> 2816 {
>> 2817 public
>> InternalSettingDelegateSingleEObjectResolvingUnsettable(ECla ss eClass,
>> EStructuralFeature feature)
>> 2818 {
>> 2819 super(eClass, feature);
>> 2820 }
>> 2821
>> 2822 @Override
>> 2823 protected boolean isUnsettable()
>> 2824 {
>> 2825 return true;
>> 2826 }
>> 2827 }
>>
>> Must the class InternalSettingDelegateSingleEObjectResolvingUnsettable
>> not inherit from InternalSettingDelegateSingleEObjectResolving instead
>> of InternalSettingDelegateSingleEObject? It seems to me that this only
>> affects reflective deserialization.
>> Thanks and cheers,
>>
>> Markus
>
Previous Topic:Standalone EMF validation not registering constraints
Next Topic:Binding XML to java: serialization of mixed content cdata, text and comments
Goto Forum:
  


Current Time: Thu Oct 24 02:24:23 GMT 2019

Powered by FUDForum. Page generated in 0.02102 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top