这个问题来自这个答案(我无法运行源代码),我的要求与此问题类似,这是一个带有应用程序控制的页面,导航到一个具有一个主视图和一个详细视图的SplitContainer。Master.view.xml已成功加载,但是我得到了
“找不到带有ID应用的控件”
单击项目时出现错误。
我的metadata.json:
"routing": {
"config": {
"routerClass": "cts.alert.MyRouter",
"viewType": "XML",
"viewPath": "cts.alert.view",
"controlId": "app",
"controlAggregation": "pages",
"clearTarget": "false",
"bypassed": {
"target": [
"notFound"
]
},
"async": true
},
"routes": [
{
"pattern": "",
"name": "worklist",
"target": [
"worklist"
]
},
{
"pattern": "split",
"name": "split",
//<SplitContainer id="idAppControl"> in SplitApp.view.xml
"view": "SplitApp",
//<App id="app"/> in App.view.xml
"targetControl": "app",
"subroutes": [
{
"pattern": "master",
"name": "main",
"view": "Master",
"targetAggregation": "masterPages",
"targetControl": "idAppControl", //SplitContainer id
"subroutes": [
{
"pattern": "VEHICLES/{objectId}",
"name": "object",
"view": "Detail",
"targetAggregation": "detailPages",
}
]
}
]
},
{
"name": "catchallMaster",
"view": "Master",
"targetAggregation": "masterPages",
"targetControl": "idAppControl",
"subroutes": [
{
"pattern": ":all*:",
"name": "catchallDetail",
"view": "NotFound"
}
]
}
],
"targets": {
"master": {
"viewName": "Master",
"viewLevel": 2,
"viewId": "master",
"controlAggregation": "masterPages"
},
"worklist": {
"viewName": "Worklist",
"viewId": "worklist",
"viewLevel": 1
},
"object": {
"viewName": "Detail",
"viewId": "detail",
"viewLevel": 3
},
"objectNotFound": {
"viewName": "ObjectNotFound",
"viewId": "objectNotFound"
},
"notFound": {
"viewName": "NotFound",
"viewId": "notFound"
},
"detailObjectNotFound": {
"viewName": "DetailObjectNotFound",
"viewId": "detailObjectNotFound"
},
"detailNoObjectsAvailable": {
"viewName": "DetailNoObjectsAvailable",
"viewId": "detailNoObjectsAvailable"
}
}
}
我不确定子路由是否仍需要这么多目标。而且我知道问题出 "targetControl" : "app"
在"split"
route中,但是如果我在route中添加“ targetControl”:“ idAppControl” "object"
,它也会产生
找不到ID为idAppControl的控件
而 这样的回答 说:
您无法加入与父路线相同的控件。
我现在真的很困惑。
而且我还尝试了删除"rootview"
in "sap.ui5"
,无法正常工作。
任何帮助都将受到欢迎!提前致谢!
感谢这个路由配置文档,我解决了我的问题。
我认为这是"targetControl": "app"
在split
导致此错误路线,但实际上它是因为"controlId": "app"
在routing.config
导致此问题。
config参数定义路由配置的默认值。
更改后,我得到另一个错误:
目标工作清单没有设置controlId且没有父项,因此无法显示目标。
所以我删除target
了worklist
route并添加targetControl: app
了它,因为它不再具有默认targetControl
值。
这是新的路由配置:
"routing": {
"config": {
"routerClass": "cts.alert.MyRouter",
"viewType": "XML",
"viewPath": "cts.alert.view",
"controlAggregation": "pages",
"clearTarget": "false",
"bypassed": {
"target": [
"notFound"
]
},
"async": true
},
"routes": [
{
"pattern": "",
"name": "worklist",
"view": "Worklist",
"targetControl": "app"
},
{
"pattern": "split",
"name": "split",
"view": "SplitApp",
"targetControl": "app",
"subroutes": [
{
"pattern": "master",
"name": "main",
"view": "Master",
"targetAggregation": "masterPages",
"targetControl": "idAppControl",
"subroutes": [
{
"pattern": "VEHICLES/{objectId}",
"name": "object",
"view": "Detail",
"targetAggregation": "detailPages"
}
]
}
]
},
{
"name": "catchallMaster",
"view": "Master",
"targetAggregation": "masterPages",
"targetControl": "idAppControl",
"subroutes": [
{
"pattern": ":all*:",
"name": "catchallDetail",
"view": "NotFound"
}
]
}
],
}
好吧,对我而言,解决方案是
"clearControlAggregation": true
在目标中使用。