IBM Support

HD88058: CATIA "CATICONTEXTUALPRODUCT" API CONTEXTUAL LINKS IS DEPRECATE D

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • Description :
    Current version of PARMOS V4 developped for CATIA
    v5r16 dyring the R16-&gtR18 migration uses
    CATIContextualProduct interface, and uses the different
    Context Management Methods of the CATIProduct
    interface.
    The CATIContextualProduct was deprecated in V5R16,
    while ContextManagement Methods where tagged
    nodoc from the beginning. As a result these methods
    should not have been used.
    However the management of contextual links is
    documented in V5R14 use case named "Working with a
    Product's Contextual Links".
    This use case did use the nodoc methods of
    CATIProduct managing contexts.
    This use case documented the usage of
    CATIContextualProduct interface. When the interface
    was marked deprecated, the sue case was removed
    without notice, neither in the what's new, nor in the
    PPR/Product page of the CAA documentation, which
    documented, and still document, its addition in
    september 2003
    Deprecation rules, as documented in the CAA
    guide "CAA V5 Authorized API Identification, Usage,
    Deprecation, and Stability" clearly states that Dassault
    System has the responsability to provide a
    documentation for which "A deprecated API shows its
    replacing Authorized API that client applications must
    use instead. This replacing Authorized API is of course
    available at the deprecation time.". This documentation
    was not provided, and furthermore, all available
    documentation of Contextual links was removed from
    CAA
    AT present, available documentation does not permit to
    understand how external references are managed by
    CATIA, as a result I do not see any possibility to re
    implement the services implemented using deprecated
    API.
    

Local fix

Problem summary

  • The CATIContextualProduct was deprecated in V5R16,
    while ContextManagement Methods where tagged
    nodoc from the beginning. As a result
    these methods
    should not have been used.
    However
    the management of contextual links is
    documented in V5R14 use case named "Working with a
    Product's Contextual Links".
    This use case did use the
    nodoc methods of
    CATIProduct
    managing contexts.
    This use case documented the usage of
    CATIContextualProduct interface. When the
    interface
    was marked deprecated, the sue
    case was removed
    without notice,
    neither in the what's new, nor in the
    PPR/Product page of the CAA documentation, which
    documented, and still document, its addition in
    september 2003
    Deprecation rules, as
    documented in the CAA
    guide "CAA
    V5 Authorized API Identification, Usage,
    Deprecation, and Stability" clearly states that Dassault
    System has the responsability to provide a
    documentation for which "A deprecated API
    shows its
    replacing Authorized API that
    client applications must
    use instead. This
    replacing Authorized API is of course
    available at the deprecation time.". This documentation
    was not provided, and furthermore, all available
    documentation of Contextual links was
    removed from
    CAA
    AT
    present, available documentation does not permit to
    understand how external references are managed by
    CATIA, as a result I do not see any
    possibility to re
    implement the services
    implemented using deprecated
    API.
    

Problem conclusion

  • THIS PROBLEM IS PERMANENT RESTRICTION IN V5R19 SP6 CATIA
    LEVEL
    Additional Closure Information:
    CATIContextualProduct is
    no more provided by DS.
    Use CATIxPDMPartItem instead.
    

Temporary fix

Comments

APAR Information

  • APAR number

    HD88058

  • Reported component name

    CAA V5 NT>XP

  • Reported component ID

    569151100

  • Reported release

    518

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-08-19

  • Closed date

    2009-10-01

  • Last modified date

    2009-10-01

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"518","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
21 August 2024