[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylyn-context-dev] MFT and EMF Client Platform
|
On 04.02.2013 20:30, Carsten Reckord wrote:
>> But it seems that it would make sense for EMF Client to adopt some sort of scheme where those local user URIs were stored in a more generic way. Or perhaps they do, but we're not treating them correctly. Looking at the code for EMFStructureBridge (L 189), I'm not sure why we're not just using the URI as is.
>
> In L189, and then further in getFile (L208), we are trying to resolve the
> parent container when the emf hierarchy ends. This is needed in order for
> model files and their folders to receive parent interest - and hence become
> visible - when an EMF object is manipulated.
>
> getFile could be done a bit prettier, but overall that looks pretty correct
> to me...
Sorry, forgot the important point: we actually do use the URI as-is for
EObjects. We just handle the containing resource specially if it points to a
workspace location.
--
Carsten Reckord
t +49 (0)561 5743277-33
f +49 (0)561 5743277-8833
e reckord@xxxxxxxx
Yatta Solutions GmbH
Sitz der Gesellschaft: Kassel
Amtsgericht Kassel, HRB 14720
USt-IdNr DE263191529
Geschäftsführung:
Johannes Jacop,
Dr. Christian Schneider
Adresse:
Ludwig-Erhard-Straße 12
34131 Kassel
Kontakt:
t +49 (0)561 5743277-0
f +49 (0)561 5743277-88
e info@xxxxxxxx
Bankverbindung:
Kasseler Bank eG
BLZ 520 900 00
Kto-Nr 158 305
