0002303: Invalid use of HasTypeDefinition between Methods in generated Nodesets

ID	Project	Category	View Status	Date Submitted	Last Update

0002303	NodeSets, XSDs and Generated Code	Implementation Bug	public	2012-12-10 10:27	2016-02-02 19:34

Reporter	Matthias Damm	Assigned To	Randy Armstrong
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed

Summary	0002303: Invalid use of HasTypeDefinition between Methods in generated Nodesets
Description	In the current tooling and the generated Nodeset files, HasTypeDefinition references are used between instance declaration methods and methods on object instances. This may be usefull information for modeling tools and SDKs but the current solution to provide this information is invalid based on Part 3. Definition in Part 3 for HasTypeDefinition ReferenceType: The SourceNode of this ReferenceType shall be an Object or Variable. Like for other information that is only needed in tooling and SDKs we should define a special XML attribute for Method nodes in the Nodeset that contains the NodeId of the corresponding instance declaration Method node. See related Mantis issue for Part 6
Tags	No tags attached.

Commit Version
Fix Due Date

Date Modified	Username	Field	Change
2012-12-10 10:27	Matthias Damm	New Issue
2012-12-10 10:56	Matthias Damm	Relationship added	related to 0002304
2013-01-02 02:04	Randy Armstrong	Status	new => resolved
2013-01-02 02:04	Randy Armstrong	Resolution	open => fixed
2013-01-02 02:04	Randy Armstrong	Assigned To	=> Randy Armstrong
2013-01-02 02:04	Randy Armstrong	Note Added: 0004385
2015-02-18 14:29	Randy Armstrong	Category	(No Category) => Implementation Bug
2016-02-02 19:34	Jim Luth	Note Added: 0006607
2016-02-02 19:34	Jim Luth	Status	resolved => closed

Randy Armstrong 2013-01-02 02:04 administrator ~0004385	Updated tooling to add MethodDeclarationId instead of adding a TypeDefinition reference to UAMethods.

Jim Luth 2016-02-02 19:34 administrator ~0006607	Closing issues that were fixed in the past.