IBM Support

PH24373: DIFFERENCE IN BEHAVIOR BETWEEN ADDSPECIFICSTEREOTYPE() AND SETSTEREOTYPE() API

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Description:
    Difference in behavior between addSpecificStereotype() and
    setStereotype() API
    
    Summary:
    There is a difference in behaviour between
    addSpecificStereotype() and setStereotype().
    
    As per API documentation there is no difference, But in the
    following usecase, We observed there is a difference in behavior
    
    Use case
    1.  Create a stereotype applicable to â ˜Object model diagramâ ™
    2.  Apply the above Stereotype on BDD via SetStereotype() api in
    java code.  â ”> The BDD gets converted to OMD.
    
    whereas while using addSpecificStereotype() or when we set the
    stereotype manually it works fine.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Rhapsody                                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Doc to be updated to detail the difference in behavior       *
    * between addSpecificStereotype() and setStereotype() API.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Description for setStereotype has been updated to reflect that
    it is now deprecated. Was relevant when Rhapsody only allowed a
    single stereotype to be applied to a model element.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH24373

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    840

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-14

  • Closed date

    2020-07-06

  • Last modified date

    2020-07-06

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"840","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
07 July 2020