I didn't come across the problem that you mention, but maybe it's because I
move packages around in a much more conservative manner.

If I want to move packages that reference each other, I will first bundle
them under one package tree. When I move them like this, there is no
problem.

I found that when you move a single package or package tree, things go quite
smoothly. When you move separate packages that reference each other, it's a
hit-and-miss affair.

I haven't tried this in 2000e, but I suspect it will not be different. (But
this is one of those cases where I'd love to be wrong!)

If Rational guys know a better method, I'm open to enlightenment.


Regards,
Huseyin Angay

Karabash Ltd.
www.karabash.co.uk



> ----------
> From:         Arne G. Styve[SMTP:[EMAIL PROTECTED]]
> Reply To:     Arne G. Styve
> Sent:         24 November 2000 14:12
> To:   rose_forum@Rational. Com
> Subject:      (ROSE) Rose Fileformat (revisited...)
> 
> 
> Hi,
> 
> I haven't given up questioning the Rose file-format yet. There are things
> still comming up when I'm working with Rose that puzzels me.
> 
> Here is one example. Davyd Norris answered a previous mail from me, where
> he
> explained thet the idea behind the .MDL-format was to be able to treat the
> MDL-file as a project file consisting of several packages of source-code
> (or
> something like that).
> 
> Well, I did. I needed to move som packages from one model to another.
> These
> packages contained diagrams showing classes which were located in other
> packages of the model (typically reverse-engineered or created from Rose
> (like the MFC6.0 import).
> 
> Now, in my new model, I have restructured the layout of packages, so the
> MFC6.0 is not located in the same "path" (Rose Browser path not file path)
> as it was in the "old" model. That's when the trouble occurse. When adding
> the packages with the previously mentioned diagrams from the old model to
> the new, Rose is not able to locate the MFC6.0 classes used in the
> diagrams.
> This is due to the "hardcoded" path stored as attributes in the .mdl file
> (see code-extract below):
> 
> .... snip ....
> 
>   superclasses        (list inheritance_relationship_list
>   (object Inheritance_Relationship
>       quid            "36CCD64E0278"
>       supplier        "Logical View::Design Model::Utilities::MFC
> 6.0::CObject
> Classes::CObject"
>       quidu           "365C7A6F009C"))
>       operations      (list Operations
>           (object Operation "Close"
>            quid               "365C7A6F00CE"
> 
> ... snip ....
> 
> I.e. the 'supplier' tag creates a major problem.
> 
> Is there an easy way to "update" my diagrams (i,e, the
> supplier-reference)?
> Since the classes referred to in my diagram does exist in my model, Rose
> should be able to locate them ? Or ?
> 
> I know it boils down to a sound architecure and all this, but on my way to
> create this architecture, operations as the one I've perfermed is
> sometimes
> neccessary.
> 
> Looking forward to any response to this query :-)
> 
> Regards
> 
> Arne
> 
> ************************************************************************
> * Rose Forum is a public venue for ideas and discussions.
> * For technical support, visit http://www.rational.com/support
> *
> * Admin.Subscription Requests: [EMAIL PROTECTED]
> * Archive of messages:
> http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
> * Other Requests: [EMAIL PROTECTED]
> *
> * To unsubscribe from the list, please send email
> *
> * To: [EMAIL PROTECTED]
> * Subject:<BLANK>
> * Body: unsubscribe rose_forum
> *
> *************************************************************************
> 
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages: 
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************

Reply via email to