Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349258 - NoRuntime attribute added to a metaonly module causes an error when loading the schema
Summary: NoRuntime attribute added to a metaonly module causes an error when loading t...
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dave Russo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-13 22:32 EDT by Sasha Slijepcevic CLA
Modified: 2011-12-05 17:28 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sasha Slijepcevic CLA 2011-06-13 22:32:02 EDT 
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.