| Method and Description |
|---|
| com.microsoft.azure.sdk.iot.service.RegistryManager.addDeviceAsync(Device)
Use the synchronous version of this API
RegistryManager.addDevice(Device). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.ServiceClient.closeAsync()
Use the synchronous version of this API
ServiceClient.close(). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.IotHubConnectionStringBuilder.createConnectionString(String)
Use
IotHubConnectionStringBuilder.createIotHubConnectionString(String) since it does not declare any thrown exceptions |
| com.microsoft.azure.sdk.iot.service.IotHubConnectionStringBuilder.createConnectionString(String, AuthenticationMethod)
Use
IotHubConnectionStringBuilder.createIotHubConnectionString(String, AuthenticationMethod) since it does not declare any thrown exceptions |
| com.microsoft.azure.sdk.iot.service.RegistryManager.createFromConnectionString(String)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
RegistryManager(String) instead since it does not declare this exception even
though it constructs the same RegistryManager. |
| com.microsoft.azure.sdk.iot.service.devicetwin.RawTwinQuery.createFromConnectionString(String)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
RawTwinQuery(String) instead
since it does not declare this exception even though it constructs the same RawTwinQuery. |
| com.microsoft.azure.sdk.iot.service.devicetwin.DeviceTwin.createFromConnectionString(String)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
DeviceTwin(String, DeviceTwinClientOptions) instead
since it does not declare this exception even though it constructs the same DeviceTwin. |
| com.microsoft.azure.sdk.iot.service.devicetwin.DeviceMethod.createFromConnectionString(String)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
DeviceMethod(String) instead
since it does not declare this exception even though it constructs the same DeviceMethod. |
| com.microsoft.azure.sdk.iot.service.jobs.JobClient.createFromConnectionString(String)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
JobClient(String) instead
since it does not declare this exception even though it constructs the same JobClient. |
| com.microsoft.azure.sdk.iot.service.devicetwin.DeviceMethod.createFromConnectionString(String, DeviceMethodClientOptions)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
DeviceMethod(String, DeviceMethodClientOptions) instead
since it does not declare this exception even though it constructs the same DeviceMethod. |
| com.microsoft.azure.sdk.iot.service.devicetwin.DeviceTwin.createFromConnectionString(String, DeviceTwinClientOptions)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
DeviceTwin(String, DeviceTwinClientOptions) instead
since it does not declare this exception even though it constructs the same DeviceTwin. |
| com.microsoft.azure.sdk.iot.service.ServiceClient.createFromConnectionString(String, IotHubServiceClientProtocol)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
ServiceClient(String, IotHubServiceClientProtocol) instead
since it does not declare this exception even though it constructs the same ServiceClient. |
| com.microsoft.azure.sdk.iot.service.ServiceClient.createFromConnectionString(String, IotHubServiceClientProtocol, ServiceClientOptions)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
ServiceClient(String, IotHubServiceClientProtocol, ServiceClientOptions) instead
since it does not declare this exception even though it constructs the same ServiceClient. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.createFromConnectionString(String, RegistryManagerOptions)
because this method declares a thrown IOException even though it never throws an IOException. Users
are recommended to use
RegistryManager(String, RegistryManagerOptions) instead since it does not declare this exception even
though it constructs the same RegistryManager. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.exportDevicesAsync(JobProperties)
Use the synchronous version of this API
RegistryManager.exportDevices(JobProperties). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.exportDevicesAsync(String, Boolean)
Use the synchronous version of this API
RegistryManager.exportDevices(String, Boolean). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.getDeviceAsync(String)
Use the synchronous version of this API
RegistryManager.getDevice(String). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.getDevices(Integer)
as of release 1.12.0. Please use
DeviceTwin.queryTwin(String sqlQuery, Integer pageSize)
to query for all devices. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.getDevicesAsync(Integer)
as of release 1.12.0. Please use
DeviceTwin.queryTwin(String sqlQuery, Integer pageSize)
to query for all devices. |
| com.microsoft.azure.sdk.iot.service.ServiceClient.getFeedbackReceiver(String)
As of release 1.1.15, replaced by
ServiceClient.getFeedbackReceiver() |
| com.microsoft.azure.sdk.iot.service.RegistryManager.getJobAsync(String)
Use the synchronous version of this API
RegistryManager.getJob(String). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.jobs.JobResult.getOutcome()
As of release 1.7.23, replaced by
JobResult.getOutcomeResult() |
| com.microsoft.azure.sdk.iot.service.RegistryManager.getStatisticsAsync()
Use the synchronous version of this API
RegistryManager.getStatistics(). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.importDevicesAsync(JobProperties)
Use the synchronous version of this API
RegistryManager.importDevices(JobProperties). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.importDevicesAsync(String, String)
Use the synchronous version of this API
RegistryManager.importDevices(String, String). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.open()
as of release 1.13.0 this API is no longer supported and open is done implicitly by the respective APIs
Opens this registry manager's executor service after it has been closed.
|
| com.microsoft.azure.sdk.iot.service.ServiceClient.openAsync()
Use the synchronous version of this API
ServiceClient.open(). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.removeDeviceAsync(String)
Use the synchronous version of this API
RegistryManager.removeDevice(Device). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.devicetwin.DeviceOperations.request(IotHubConnectionString, URL, HttpMethod, byte[], String, long) |
| com.microsoft.azure.sdk.iot.service.ServiceClient.sendAsync(String, Message)
Use the synchronous version of this API
ServiceClient.send(String, Message). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.devicetwin.Query.sendQueryRequest(IotHubConnectionString, URL, HttpMethod, Long) |
| com.microsoft.azure.sdk.iot.service.Message.setDeliveryAcknowledgement(DeliveryAcknowledgement)
as of service-client version 1.15.1, please use
Message.setDeliveryAcknowledgementFinal(DeliveryAcknowledgement) |
| com.microsoft.azure.sdk.iot.service.Configuration.setForceUpdate(Boolean)
This method currently only validates forceUpdate parameter
|
| com.microsoft.azure.sdk.iot.service.BaseDevice.setForceUpdate(Boolean)
This method currently only validates forceUpdate parameter
|
| com.microsoft.azure.sdk.iot.service.JobProperties.setJobId(String) |
| com.microsoft.azure.sdk.iot.service.auth.SymmetricKey.setPrimaryKey(String)
as of service-client version 1.15.1, please use
SymmetricKey.setPrimaryKeyFinal(String) |
| com.microsoft.azure.sdk.iot.service.auth.SymmetricKey.setSecondaryKey(String)
as of service-client version 1.15.1, please use
SymmetricKey.setSecondaryKeyFinal(String) |
| com.microsoft.azure.sdk.iot.service.BaseDevice.setThumbprint(String, String)
as of service-client version 1.15.1, please use
BaseDevice.setThumbprintFinal(String, String) |
| com.microsoft.azure.sdk.iot.service.RegistryManager.updateConfiguration(Configuration, Boolean)
the forceUpdate argument does nothing so this method will always behave the same as @link #updateConfiguration(Configuration)}
|
| com.microsoft.azure.sdk.iot.service.devicetwin.DeviceTwin.updateDesiredProperties(DeviceTwinDevice)
Use
DeviceTwin.updateTwin(DeviceTwinDevice device) to update desired properties. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.updateDevice(Device, Boolean)
The forceUpdate argument does nothing so this method will always behave the same as
RegistryManager.updateDevice(Device) |
| com.microsoft.azure.sdk.iot.service.RegistryManager.updateDeviceAsync(Device)
Use the synchronous version of this API
RegistryManager.updateDevice(Device). This asynchronous
API only spawned a thread to run the synchronous API, so users are advised to do this themselves
in order to have control over the spawned threads. |
| com.microsoft.azure.sdk.iot.service.RegistryManager.updateDeviceAsync(Device, Boolean)
The forceUpdate argument does nothing so this method will always behave the same as
RegistryManager.updateDeviceAsync(Device) |
| com.microsoft.azure.sdk.iot.service.RegistryManager.updateModule(Module, Boolean)
The forceUpdate argument does nothing so this method will always behave the same as @link #updateModule(Module)}
|
Copyright © 2022. All rights reserved.