why there are two duplicate metadata requests

Created by Jerry Wang, last modified on Mar 03, 2015

  • ODataModel
    why there are two duplicate metadata requests
    Actually they are not duplicated:
  1. the first one has accept type as xml, while the second one pure text.
  2. the prefix of the two are different: /sap and /1sap.
    First request:
    Trigger point: main view constructor is called:
    why there are two duplicate metadata requests
    sap.ca.scfld.md.Startup.init is called in our application code:
    why there are two duplicate metadata requests
    ConnectionManager.getNewInstance is called with configuration data maintained in file Configuration.js:
why there are two duplicate metadata requestswhy there are two duplicate metadata requests OData model instance is created based on this relative url: why there are two duplicate metadata requests first request is sent out with relative url: why there are two duplicate metadata requests second request: why there are two duplicate metadata requests The application code is triggering the second request sent: why there are two duplicate metadata requests The configuration comes from component metadata: why there are two duplicate metadata requestswhy there are two duplicate metadata requests

要获取更多Jerry的原创文章,请关注公众号"汪子熙":
why there are two duplicate metadata requests