Prosys OPC UA Java SDK 1.5.0
This is a new release of the SDK. There are various compliance improvements and fixes in here.
OPC Foundation Java Stack changes
- Build 1.01.330.16
- New: Multidimensional index ranges with NumericRange
- New: DataValue.clone
- Fixed: Handle empty server certificate (the same way as null)
- Fixed: UnsignedLong constructor with BigInteger (equal to Long.MAX_VALUE)
Changes to both SDK Client and Server
- Changed: MonitoredDataItem.get/setIndexRange(), datatype changed from String to NumericRange
- Fixed: Enumeration DataType was not linked to Integer.class
- Fixed: DataTypeConverter.convert to throw consistently ClassCastException also when values are out of range and cannot be converted
Changes to SDK Client
- New: Subscription.getSetMaxMonitoredItemsPerCall()
- Fixed: historyReadAll in case the server returns null with Good_NoData
Changes to SDK Server
- Interface change: SubscriptionManager.createMonitoredDataItem(), data type of indexRange parameters changed from String to NumericRange
- Interface change: SubscriptionManagerListener.onCreateMonitoredDataItem(), data type of indexRange parameters changed from String to NumericRange
- Interface change: NodeManager.createMonitoredDataItem(), data type of indexRange parameters changed from String to NumericRange
- Interface change: NodeManagerListener.onCreateMonitoredDataItem(), data type of indexRange parameters changed from String to NumericRange
- Changed: PlainVariable/PlainInstanceVariable.setCurrentValue() to default to DateTime.currentTime instead of null for SourceTimestamp
- New: IoManager.applyIndexRangeToReadValue()
- New: IoManager.applyIndexRangeToWrittenValue()
- New: IoManager.checkIndexRange()
- New (overload): MonitoredDataItem.notifyDataChange(value, applyIndexRange)
- ServiceHandler.set/getMaxOperationsPerRequest
- SubscriptionServiceHandler.set/getMaxMonitoredItemsPerCall
- AttributeServiceHandler.set/getMaxNodesPerRead
- AttributeServiceHandler.set/getMaxNodesPerWrite
- AttributeServiceHandler.set/getMaxNodesPerHistoryReadData
- AttributeServiceHandler.set/getMaxNodesPerHistoryReadEvents
- AttributeServiceHandler.set/getMaxNodesPerHistoryUpdate
- NodeManagementServiceHandler.set/getMaxNodesPerBrowse
- NodeManagementServiceHandler.set/getMaxNodesPerMethodCall
- NodeManagementServiceHandler.set/getMaxNodesPerNodeManagement
- NodeManagementServiceHandler.set/getMaxNodesPerRegisterNodes
- NodeManagementServiceHandler.set/getMaxNodesPerTranslateBrowsePathsToNodeIds
- Fixed: readAttribute was modifying the userAccessLevel that it got from user code - in effect reducing READWRITE to READONLY if it was provided.
- Fixed: readAttribute was modifying the userWriteMask that it got from user code (similar to userAccessLevel)
- Fixed: enumeration values could not be written (because of the linkage problem, see above)
- Fixed: IoManager.checkAccessLevel, possible NPE
- Fixed: Session.authenticationToken must be initialized uniquely, to avoid reconnect problems in server restart.
- Some CTT-related (Compliance Test Tool) fixes
24.06.14