-----Original Message-----
From: Nagesh HR [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 24, 2002 10:29 PM
To: [EMAIL PROTECTED]
Cc: Hsia, John
Subject: Add-In Questions??
Hi All
We are having our own Add-in, that converts the Rose Model to Database model. We are facing some problems with respect to REI, and its usage.
Each class is mapped to Table in Database, and each properties into column. We have customized Add-in property for RoseAttribute called "ColumnSeqNo", based on this value the table column structure will be defined.
With respect to abstract base class(ABC) concept, we will not have the Table for the base class, and all its properties will be part of the derived class table. In this case, all the ABC properties will be listed along with derived class properties for specifying column sequence no. In our example, if Employee is ABC, then all its properties will be made part of Manager as well as Doctor. For all practical purposes, the ABC properties will be treated as if they were defined for derived class. So, for the same ABC property, there could be different ColumnSeqNo in different derived classes.
Please find the example in the Attachment
The problems are :
1. How to persist same ABCs property's different ColumnSeqNo information for different derived classes in .mdl/.cat file.
with respect the diagram in the example,
As Employee class is ABC, hence all its properties will be part of Manager class and as well as Doctor class. Here, Employee class will not have Table, and the derived classes Doctor, and Manager will have Tables.
The EmpNo attribute in Employee class will be column in Manager Table as well as in Doctor Table, but the column ordering for EmpNo may be different in Manager Table to that of Doctor Table. But EmpNo RoseAttribute's Addin property ColumnSeqNo can take only one value. How to have the different ColumnSeqNo's for different derived classes
One of Our Approach to solve the above problem is
a) have another addin RoseClass property say "BaseColumnSeqNos". In derived class, we will store concatenated string for each base attribute "<BaseAttribute:ColumnSeqNo>"Is any better approach ???
2. How to suppress specific attributes from class diagram view ?? Rose provides only SuppressAttributes API which will suppress all attributes.
3. How to make customised Add-In property non-editable in the RoseView, but should be able to modify programmatically ??
4. How to hide any particular / All customised properties for specific classes ??
<<RoseForum.jpg>>
Any Suggestions / Solutions / Help is welcome
Thanks and Regards
Nagesh H R
Title: Add-In Questions??
#2.
Not programmatically possible today.
#3.
Can only set visibility at a tool level today.
#4.
Properties created on an individual element without support from a pty file or
defined as part of model.DefaultProperties are not visible. An alternative
is to use sets - i.e. within a tool have different sets with different
values. Then either programmatically or through user gestures, selecting
different sets will result in different properties being displayed. This
technique is used extensively in the J2EE add-in for Rose.
