0001315: Conversion Rules bteween ByteString and Byte[] Must be Clarified

ID	Project	Category	View Status	Date Submitted	Last Update

0001315	10000-004: Services		public	2010-07-27 17:48	2012-02-09 22:42

Reporter	Randy Armstrong	Assigned To	Matthias Damm
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Fixed in Version	1.02

Summary	0001315: Conversion Rules bteween ByteString and Byte[] Must be Clarified
Description	Scenario needs to be explained properly - i.e. receivers must always be prepared to deal with a ByteString when they expect a Byte[] Problem does not exists for dimensions > 2
Tags	No tags attached.

Commit Version
Fix Due Date

Matthias Damm 2011-03-07 18:21 developer ~0002340	Telco March 7, 2011 Find places where Bad_TypeMismatch is used e.g. Write and clarify that ByteString can be used where a Byte[] is requested.

Matthias Damm 2011-03-12 13:24 developer ~0002373	Added clarification to Table 55 and 63: A ByteString is structurally the same as a one dimensional array of Byte. A server shall accept a ByteString if an array of Byte is expected. Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc"

Randy Armstrong 2011-05-23 16:55 administrator ~0002742	Discuessed in Walldorf

Date Modified	Username	Field	Change
2010-07-27 17:48	Randy Armstrong	New Issue
2010-07-27 17:48	Randy Armstrong	Relationship added	related to 0001314
2010-07-27 17:48	Randy Armstrong	Status	new => assigned
2010-07-27 17:48	Randy Armstrong	Assigned To	=> Matthias Damm
2011-03-07 18:21	Matthias Damm	Note Added: 0002340
2011-03-12 13:24	Matthias Damm	Status	assigned => resolved
2011-03-12 13:24	Matthias Damm	Resolution	open => fixed
2011-03-12 13:24	Matthias Damm	Note Added: 0002373
2011-05-23 16:55	Randy Armstrong	Status	resolved => closed
2011-05-23 16:55	Randy Armstrong	Note Added: 0002742
2012-02-09 22:42	Jim Luth	Fixed in Version	=> 1.02