IBM Support

LO75185: XPAGES DOJO.REQUIRE() LOADS XSPCLIENTDOJO IN DEBUG MODE

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

  • When an XPage is opened via the browser the HTML shows
    XSPClientDojo loading as a script library:
    .
    <head>
    <title></title>
    <script type="text/javascript"
    src="/xsp/.ibmxspres/dojoroot-1.6.1/dojo/dojo.js"
    djConfig="locale: 'en-us'"></script>
    <script type="text/javascript"
    src="/xsp/.ibmxspres/dojoroot-1.6.1/ibm/xsp/widget/layout/layers
    /xspClientDojo.js"></script>
    </head>
    
    However when debug versions of JS are enabled in the DB e.g.
    via xsp.client.script.dojo.version=1.6.1-debug , xspClientDojo
    is suddenly emitted as a dojo.require() call instead:
    
    <head>
    <title></title>
    <script type="text/javascript"
    src="/domjs/dojo-1.6.1-debug/dojo/dojo.js" djConfig="locale:
    'en-us'"></script>
    <script
    type="text/javascript">dojo.require('ibm.xsp.widget.layout.xspCl
    ientDojo')</script>
    </head>
    
    With xspClientDojo loading in a dojo.require() this causes
    problems with with other <xp> tags on the Xpage. For example,
    the
    <xp:fileUpload> tag emits JS in the source that looks like this:
    
    <script
    type="text/javascript">if(XSP.getElementById("view:_id1")!=null)
    XSP.getElementById("view:_id1").encoding="multipart/form-data";<
    /script>
    .
    Note that this is not wrapped in a dojo.ready() call -- it's
    just straight JS. If the browser is slow for example IE8
    and/or the JS libraries take awhile to download, XSP may not
    have instantiated yet because the dojo.require() is still being
    processed. This causes a browser-level hard JS error "'XSP' is
    undefined". When debug mode is NOT used all is OK because the
    browser loads the library before running any JS at all.
    

Local fix

Problem summary

  • A programming error was found and will be corrected in a future
     release.
    

Problem conclusion

  • A programming error was found and will be corrected in a future
     release.
    

Temporary fix

Comments

  • This APAR is associated with SPR# RDJS97FM86.
    A programming error was found and will be corrected in a future
     release.
    

APAR Information

  • APAR number

    LO75185

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    852

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-06

  • Closed date

    2014-04-25

  • Last modified date

    2014-04-25

  • 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

    DOMINO SERVER

  • Fixed component ID

    5724E6200

Applicable component levels

  • R852 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 April 2014