IBM Support

PK84447: CONTENT.GETID() RETURNS JCR UUID RANDOMLY

 

APAR status

  • Closed as program error.

Error description

  • content.getID() returns JCR UUID randomly
    
    <IDCmpnt context="current" type="content" field="name"/>
    randomly
    prints JCR ID instead of WCM contentID.
    com.ibm.workplace.wcm.api.
    Content.getId() is also returning JCR UUID.
    

Local fix

Problem summary

  • content.getId() and content.getId().getName() return the UUID as
    the content name after syndication
    .
    Under certain circumstances when content is syndicated to the
    subscriber it is first created/stored using the UUID instead of
    the name.  Content items are then renamed later in the
    syndication process.  These renamed content items may return the
    UUID for the items name when using content.getId() and
    content.getId().getName()
    STEPS:
    1) Customer created content with custom coded UI that created
    the content as follows:
         When content is being updated (let's say content name is
    "content1"),
         New draft is created ("content2").
         Then old content is renamed to "content1temp"
         New draft is renamed to "content1" and published.
         Then "content1temp" is archived.
    2) When this data is syndicated it is given the UUID as its name
    upon initial syndication.  At this stage the UUID is the name of
    the content.
    .
         3.4.2009 22:33:47:585 EEST  00001b21 IdentityContr 3
    Setting 'ibmcontentwcm:name' = 017478004d9ca78fa92ce9c0e26b6f9c
    .
    3) Later the content is renamed to the appropriate name
    "content1" but the rename method does not remove the item from
    the cache if it is cached and therefore the .
    .
         3.4.2009 22:35:48:680 EEST  00001b21 PackageProces 2
    Renaming   {017478004d9ca78fa92ce9c0e26b6f9c,
    com.aptrix.pluto.content.Content} to 21238782977046_429500,
    draft=false
    

Problem conclusion

  • Under certain circumstances when content is syndicated to the
    subscriber it is first created/stored using the UUID instead of
    the name.  If the item is cached prior to the rename it is
    cached with the UUID as the name and API methods like
    content.getId() and content.getId().getName() will return the
    UUID as the name.
         3.4.2009 22:33:47:585 EEST  00001b21 IdentityContr 3
    Setting 'ibmcontentwcm:name' = 017478004d9ca78fa92ce9c0e26b6f9c
    Later the content is renamed to the correct name but the cache
    is not cleared therefore content.getId() and
    content.getId().getName() continue to return the UUID as the
    items name.
    .
    This fix results in the cache being cleared when the content is
    renamed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK84447

  • Reported component name

    LOTUS WEB CONT

  • Reported component ID

    5724I2900

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-09

  • Closed date

    2009-05-11

  • Last modified date

    2009-05-11

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

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

Modules/Macros

  • WCM
    

Fix information

  • Fixed component name

    LOTUS WEB CONT

  • Fixed component ID

    5724I2900

Applicable component levels

  • R60J PSY

       UP

  • R60H PSY

       UP

  • R61A PSY

       UP

[{"Business Unit":{"code":"BU051","label":"N\/A"},"Product":{"code":"SUPPORT","label":"IBM Web Content Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB33","label":"N\/A"}}]

Document Information

Modified date:
20 December 2021