| Proxy Resolution Problem [message #660373] |
Fri, 18 March 2011 03:42  |
Eclipse User |
|
|
|
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 04:21  |
| Eclipse User |
|
|
|
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 09:41 |
| Eclipse User |
|
|
|
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
>
|
|
|
Powered by
FUDForum. Page generated in 0.03698 seconds
Home