Bugzilla – Full Text Bug Listing
| Summary: | NoRuntime attribute added to a metaonly module causes an error when loading the schema | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Sasha Slijepcevic <sascha> |
| Component: | Core | Assignee: | Dave Russo <d-russo> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d-russo, dfriedland |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
If both 'metaonly' qualifier and NoRuntime attribute are in the specification for a module, when the schema for that package is loaded, an XDC runtime error is raised. A simple test case can be created from basic.mconf in the xdctest tree. If the attribute NoRuntime is added to basic.mconf.pkgA.PConf, and the package basic.mconf.client is built, the following error message is displated: js: "./package/cfg/main_p64P.cfg", line 168: XDC runtime error: pkgA.PConf: no element named 'common$' This is caused by calling Value.Obj.put with a new property 'common$' as an argument. New properties are never added using 'put', they are added using 'bind'. At the time put("common$") is invoked, 'common$' is normally already added to a module when the module inherits from IModule. However, metaonly modules do not inherit from IModule.