前往小程序,Get更优阅读体验!
立即前往
首页
学习
活动
专区
工具
TVP
发布
社区首页 >专栏 >why there are two duplicate metadata requests

why there are two duplicate metadata requests

作者头像
Jerry Wang
发布2019-09-17 11:36:44
5110
发布2019-09-17 11:36:44
举报

版权声明:本文为博主原创文章,遵循 CC 4.0 BY-SA 版权协议,转载请附上原文出处链接和本声明。

本文链接:https://cloud.tencent.com/developer/article/1506754

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

  • ODataModel

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:

sap.ca.scfld.md.Startup.init is called in our application code:

ConnectionManager.getNewInstance is called with configuration data maintained in file Configuration.js:

OData model instance is created based on this relative url:

first request is sent out with relative url:

second request:

The application code is triggering the second request sent:

The configuration comes from component metadata:

本文参与 腾讯云自媒体分享计划,分享自作者个人站点/博客。
原始发表:2019年09月16日,如有侵权请联系 cloudcommunity@tencent.com 删除

本文分享自 作者个人站点/博客 前往查看

如有侵权,请联系 cloudcommunity@tencent.com 删除。

本文参与 腾讯云自媒体分享计划  ,欢迎热爱写作的你一起参与!

评论
登录后参与评论
0 条评论
热度
最新
推荐阅读
目录
  • Created by Jerry Wang, last modified on Mar 03, 2015
领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档