Hi Davyd,

I discovered how to replicate the problem. Unfortunately I can't mail the
source file, seeing as how it's company confidential.

What appears to be happening, is that when I import a structure that has
attributes of different types, Rose sorts the attributes by type before
importing.

So if my structure contains a 'string' followed by 'integer', followed by
'string', say, it will be imported as 'integer', 'string', 'string'.

My version of Rose is 7.5.0103.1920.

Hope this helps.

Les.



                                                                                       
           
                    "Norris,                                                           
           
                    Davyd"               To:     "'[EMAIL PROTECTED]'"           
           
                    <dnorris@rati        <[EMAIL PROTECTED]>, 
[EMAIL PROTECTED]       
                    onal.com>            cc:                                           
           
                                         Subject:     RE: (ROSE) Reverse Engineering 
IDL          
                    07/05/2001                                                         
           
                    10:58 PM                                                           
           
                                                                                       
           
                                                                                       
           




Hi Les,

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
[...]
> So my database person and I have just done an experiment to
> see where the
> data got sorted, and it appears that Rose is changing the order of the
> attributes as it imports the IDL into classes. In fact, Rose
> seems to be
> scanning for attributes of the same type, importing them all
> together and
> then looking for subsequent types. There seems to be no logic
> to the order
> in which the IDL is imported.
>
> Has anyone else out there experienced this?

What version of Rose are you using? I have just repeated this with rose
2001
and 2001a and cannot replicate this behaviour. I have done both reverse and
RTE of corba structs and interfaces and the attributes in the model stayed
exactly in the order in which they were defined.

>
> Does anyone have a recommendation for how to get the
> attributes in their
> correct order in the classes.

Apart from the fact that this did not happen when I did it, I also have a
list in the specification dialog box for the struct or interface which
allows me to explicitly order and reorder the attributes. You could use
this
to fix your model, but given the volume of IDL you mentioned, I would try
to
figure out why your model was reordered in the first place!!

>
> Can anyone tell me what I did wrong so that this won't happen
> next time I
> am asked to document some IDL (or other type of object data)?

Ummmmm, maybe you did not face North and spit over your left shoulder???
Honestly I can't reproduce your problem with the versions of Rose I am
using.

The only other thing I can think of is that they moved round during the
export to Word - how did you do this? SoDA? The Rose API?

Can you tell me:
 - your Rose version and patch level
 - look in your model and let me know if they are in order in the model
 - how you did the export

Regards,

Dave.
--
Davyd Norris - Consultant
Regional Services Organisation (Asia Pacific)
Rational Software
Level 2, 459 Collins Street
Melbourne, Vic 3000
Australia.
Phone: +61 3 9613 9632
Fax  : +61 3 9613 9699
HDesk: +61 2 9419 0111
--




************************************************************************
* 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