Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Being Able to React to Failed Service Metadata Request Sent by ODataModel Defined in App Descriptor

See original GitHub issue

This is more an enhancement request.

Motivation

Currently, the best practice is to set the ODataModel on the Component via the app descriptor (manifest.json) enabling preload and manifest first approach.

"models": {
  "myODataModel": {
    "dataSource": "mainService",
    "settings": {
      "preliminaryContext": true
    },
    "preload": true
}

Since the metadata is thus requested as early as possible, attaching a "metadataFailed" event handler in Component.js is often too late due to a race condition.

return UIComponent.extend("my.Component", {
  metadata: {
    manifest: "json"
  },

  init: function() {
      UIComponent.prototype.init.apply(this, arguments);
      this.getModel("myODataModel").attachMetadataFailed(/*...*/); // Too late ☹️
  },
});

Luckily, there is the API isMetadataLoadingFailed which can be leveraged to build a custom thenable method, but it would be more convenient if the framework could provide such a method out-of-the-box.

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:8 (8 by maintainers)

Top GitHub Comments

2reactions

uhlmannmcommented, Jun 19, 2020

As of SAPUI5 1.79 sap.ui.model.odata.v2.ODataModel#metadataLoaded has an optional parameter bRejectOnFailure. When set to true the returned promise will be rejected if the initial loading of the metadata fails. Hence closing this issue.

0reactions

uhlmannmcommented, May 19, 2020

@boghyon : Thank you for testing! I will close this issue when the functionality is shipped.

Best regards Mathias.