问题描述
我正在 HANA Cloud Platform Fiori启动板中将testshell项目作为"Shell插件"运行.当我在默认首页(包含所有图块)中访问启动板时，shell插件加载正确.
I am running a testshell project as "Shell plugin" in the HANA Cloud Platform Fiori Launchpad. When I visit the Launchpad in the default front page (with all the tiles), the shell plugin is loaded right.
我的Shell插件修改了导航URL中的某些内容，因此，我必须确保在加载应用程序之前先加载Shell插件' Component.js .
My shell plugin modifies some things in the navigation URL's, so I must ensure, that the shell plugin is loaded before the applications' Component.js is loaded.
但是，当我以特定的意图启动Fiori Launchpad时(例如 https://HCP_URL/hrtest# requestleave-Display )，则首先加载应用程序 requestleave 的 Component.js ，然后再加载外壳插件的 Component.js
But, when I start the Fiori Launchpad with a specific intent (for example https://HCP_URL/hrtest#requestleave-Display), the Component.js of the application requestleave is loaded first and then the shell plugins' Component.js.
在此处的文档中 https://help.hana.ondemand .com/cloud_portal_flp/frameset.htm?87764543e31247b5b471c06e3f6da6fc.html 我读到:
From the documenation here https://help.hana.ondemand.com/cloud_portal_flp/frameset.htm?87764543e31247b5b471c06e3f6da6fc.html I read:
我如何确保在为给定应用程序创建组件之前先加载并初始化shell插件?
How can I ensure, that the shell plugin is loaded and initialized before it creates Components for the given applications?
推荐答案
该应用在实际发生插件之前已加载.这里的主要目的是加载插件不应减慢FLP/应用程序的启动速度.这就是为什么在插件初始化之前启动应用程序初始化的原因.当前尚无办法解决此问题.
That the app is loaded before the plugin is actually intended behavior. The main take here is that loading a plugin should not slow down the FLP/Application startup. This is why app initialization is started before plugin initialization.Currently there is no way to overcome this behavior.
为什么在启动应用程序之前需要操纵URL?请提供更多信息，以便我们也许可以提出其他选择.
Why do you require to manipulate the URL before starting the app? Please provide more information so that we I can perhaps come up with an alternative.
这篇关于在创建应用程序组件之前启动Fiori Shell插件.如何?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！