|
| Re: Reloading one resource removes stereotypes from another [message #472877 is a reply to message #472871] |
Tue, 08 May 2007 20:49  |
 james bruck
Messages: 1724
Registered: July 2009 |
Senior Member |
|
|
Hi Billy,
That doesn't sound good. Can you raise a defect on that and it will be
looked into in more detail. Please attach .uml models.
Cheers,
- James.
"Billy Dennigan" <bdennigan@curamsoftware.com> wrote in message
news:op.trzw1pn6j2jq2z@kilo.curamsoftware.com...
Hi,
We're having probems with models which are stored across two or more files.
For example: we have a pair of nested packages (packagedElement)
'ParentPackage' and 'ChildPackage' whereby
'ParentPackage' contains 'ChildPackage', 'ParentPackage' is stored in
ParentFile.mdl, and 'ChildPackage' is stored in ChildFile.mdl
Both of these packagedElements have a stereotype from our profile applied.
So in ParentFile.mdl we see something like:
<packagedElement xmi:type="uml:Package"
href="ChildFile.mdl#_7hFkcPFwEduBy7DMwGCuwQ"/>
The model can be very large so we want to be able to reload parts of it
from disk without reloading the whole thing.
The obvious way to do this is to unload and reload individual resources
whenever they change on disk.
However the problem is that whenever I unload and reload the Resource for
ParentPackage.mdl, the stereotypes for everything in ChildPackage.mdl (or
any other 'nested' files) get unapplied. i.e. calling
'getAppliedStereotypes' on anything from this resource returns an empty
array.
The only way around this so far is to also reload the resource for
ChildPackage.mdl. But this has a cascading effect because once you reload
a 'child' resource, you lose the stereotypes of its 'child' resources and
must reload them, and so on.
Does our approach sound correct, or are we missing something here? Any
help would be much appreciated.
Thanks in advance.
Billy Dennigan.
|
|
|
| Re: Reloading one resource removes stereotypes from another [message #614518 is a reply to message #472871] |
Tue, 08 May 2007 20:49 |
james bruck
Messages: 1724
Registered: July 2009 |
Senior Member |
|
|
Hi Billy,
That doesn't sound good. Can you raise a defect on that and it will be
looked into in more detail. Please attach .uml models.
Cheers,
- James.
"Billy Dennigan" <bdennigan@curamsoftware.com> wrote in message
news:op.trzw1pn6j2jq2z@kilo.curamsoftware.com...
Hi,
We're having probems with models which are stored across two or more files.
For example: we have a pair of nested packages (packagedElement)
'ParentPackage' and 'ChildPackage' whereby
'ParentPackage' contains 'ChildPackage', 'ParentPackage' is stored in
ParentFile.mdl, and 'ChildPackage' is stored in ChildFile.mdl
Both of these packagedElements have a stereotype from our profile applied.
So in ParentFile.mdl we see something like:
<packagedElement xmi:type="uml:Package"
href="ChildFile.mdl#_7hFkcPFwEduBy7DMwGCuwQ"/>
The model can be very large so we want to be able to reload parts of it
from disk without reloading the whole thing.
The obvious way to do this is to unload and reload individual resources
whenever they change on disk.
However the problem is that whenever I unload and reload the Resource for
ParentPackage.mdl, the stereotypes for everything in ChildPackage.mdl (or
any other 'nested' files) get unapplied. i.e. calling
'getAppliedStereotypes' on anything from this resource returns an empty
array.
The only way around this so far is to also reload the resource for
ChildPackage.mdl. But this has a cascading effect because once you reload
a 'child' resource, you lose the stereotypes of its 'child' resources and
must reload them, and so on.
Does our approach sound correct, or are we missing something here? Any
help would be much appreciated.
Thanks in advance.
Billy Dennigan.
|
|
|
Powered by
FUDForum. Page generated in 0.02327 seconds
] 
Search
Help
Register
Login
Home
