Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » UML2 » cross reference to models in other project not resolved
cross reference to models in other project not resolved [message #477120] Tue, 25 March 2008 12:30 Go to next message
Jinhui is currently offline JinhuiFriend
Messages: 42
Registered: July 2009
Member
Hi guys,

I have a problem about inter model references: if the type of a Property
is defined in a model in the same project, the type can be resolved. But
if the type is defined in a model in the other Project(i.e. not in the
same project as the referencing model), then the Type can't be resolved,
it was just an eProxy.

the situation:

I have two projects:
--ProjectA
|--java.emx
|--Date (uml::Class)

--ProjectB
|--Models
|--myModel.emx (imported "platform:/resource/ProjectA/java.emx")
|--Class1.attr1,
type="platform:/resource/ProjectA/java.emx#XMI_ID?/Date?"

Now the problem here: if I try to get the type of attr1, it is defined as
a eProxy, so the name of the type of Class1.attr1 is in this case "null".

But interestingly, if I move java.emx into the same Project as the
referencing model, i.e. ProjectB, the the model can be resolved correctly.
I get the name of type of Class1.attr1 == "Date".

Can anyone explain this to me? Does this mean that I have to copy the
referenced Model into every Project that references it???

best Regards!
Jinhui
Re: cross reference to models in other project not resolved [message #477138 is a reply to message #477120] Wed, 26 March 2008 22:06 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Jinhui,

It appears that you are working with .emx files which have slightly
different ways of serializing references than the UML2 project does.
You definitely do not have to copy around the referenced model.
From RSA, try to export the .emx files to .uml files and then try the same
scenario. Does it happen with the .uml files also?
Can you post any exceptions or stack trace that you are getting?

- James.


"Jinhui" <zhuj@in.tum.de> wrote in message
news:68b66082e0c9a6da837263865a00cecf$1@www.eclipse.org...
> Hi guys,
> I have a problem about inter model references: if the type of a Property
> is defined in a model in the same project, the type can be resolved. But
> if the type is defined in a model in the other Project(i.e. not in the
> same project as the referencing model), then the Type can't be resolved,
> it was just an eProxy.
>
> the situation:
>
> I have two projects:
> --ProjectA
> |--java.emx
> |--Date (uml::Class)
>
> --ProjectB
> |--Models
> |--myModel.emx (imported "platform:/resource/ProjectA/java.emx")
> |--Class1.attr1,
> type="platform:/resource/ProjectA/java.emx#XMI_ID?/Date?"
>
> Now the problem here: if I try to get the type of attr1, it is defined as
> a eProxy, so the name of the type of Class1.attr1 is in this case "null".
> But interestingly, if I move java.emx into the same Project as the
> referencing model, i.e. ProjectB, the the model can be resolved correctly.
> I get the name of type of Class1.attr1 == "Date".
>
> Can anyone explain this to me? Does this mean that I have to copy the
> referenced Model into every Project that references it???
>
> best Regards!
> Jinhui
>
Re: cross reference to models in other project not resolved [message #626272 is a reply to message #477120] Wed, 26 March 2008 22:06 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Jinhui,

It appears that you are working with .emx files which have slightly
different ways of serializing references than the UML2 project does.
You definitely do not have to copy around the referenced model.
From RSA, try to export the .emx files to .uml files and then try the same
scenario. Does it happen with the .uml files also?
Can you post any exceptions or stack trace that you are getting?

- James.


"Jinhui" <zhuj@in.tum.de> wrote in message
news:68b66082e0c9a6da837263865a00cecf$1@www.eclipse.org...
> Hi guys,
> I have a problem about inter model references: if the type of a Property
> is defined in a model in the same project, the type can be resolved. But
> if the type is defined in a model in the other Project(i.e. not in the
> same project as the referencing model), then the Type can't be resolved,
> it was just an eProxy.
>
> the situation:
>
> I have two projects:
> --ProjectA
> |--java.emx
> |--Date (uml::Class)
>
> --ProjectB
> |--Models
> |--myModel.emx (imported "platform:/resource/ProjectA/java.emx")
> |--Class1.attr1,
> type="platform:/resource/ProjectA/java.emx#XMI_ID?/Date?"
>
> Now the problem here: if I try to get the type of attr1, it is defined as
> a eProxy, so the name of the type of Class1.attr1 is in this case "null".
> But interestingly, if I move java.emx into the same Project as the
> referencing model, i.e. ProjectB, the the model can be resolved correctly.
> I get the name of type of Class1.attr1 == "Date".
>
> Can anyone explain this to me? Does this mean that I have to copy the
> referenced Model into every Project that references it???
>
> best Regards!
> Jinhui
>
Previous Topic:EMF and UML2 M5 install issue
Next Topic:constraint's severity
Goto Forum:
  


Current Time: Fri Apr 26 07:17:43 GMT 2024

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

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

Back to the top