PI27036: Duplicate[RATLC02859830]: Dependencies are recognized different by the Rhapsody Java API

Rational Rhapsody 8.1.2

APAR status

• Closed as program error.

Error description

• Description
  -----------
  The behavior is observed for the model in Rhapsody on having
  simple Dependencies (without stereotype). The API method
  getMetaclass() returns different metaclass for the end elements
  of the dependency.
  
  The dependencies are created from a File element to a  Part
  (Object) element.
  
  -if the dependency was created in browser (from the context menu
  of the dependent element)
  dependent: file_1 - metaclass: Class
  dependsOn: part_0 - metaclass: Class
  
  -if the dependency was drawn on the diagram from the drawing
  toolbar
  dependent: file_6 - metaclass: Module
  dependsOn: part_5 - metaclass: Object
  
  Please find the screen shots of the Rhapsody model and also of
  the sample Java code.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the API method getMetaclass() is called for a
  dependency, the metaclass returned is different depending on
  how the dependency was created: by adding it in the browser
  or by drawing it on a diagram.
  

Problem conclusion

• Fixed in 8.1.2
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TLOGIC RHAPSODY

• Fixed component ID

  5724V74RP

Applicable component levels

• R806 PSN

     UP