|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
| Deprecated Methods | |
|---|---|
| net.rim.pushsdk.subscription.SubMemoryDAOImpl.batchIncrementConsecutiveFailedPushCount(List |
|
| net.rim.pushsdk.subscription.SubRDBMSDAOImpl.batchIncrementConsecutiveFailedPushCount(List |
|
| net.rim.pushsdk.subscription.SubscriptionDAO.batchIncrementConsecutiveFailedPushCount(List As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionService.batchIncrementConsecutiveFailedPushCount(List As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.batchIncrementConsecutiveFailedPushCount(List |
|
| net.rim.pushsdk.subscription.SubMemoryDAOImpl.batchResetConsecutiveFailedPushCount(List |
|
| net.rim.pushsdk.subscription.SubRDBMSDAOImpl.batchResetConsecutiveFailedPushCount(List |
|
| net.rim.pushsdk.subscription.SubscriptionDAO.batchResetConsecutiveFailedPushCount(List As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionService.batchResetConsecutiveFailedPushCount(List As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.batchResetConsecutiveFailedPushCount(List |
|
| net.rim.pushsdk.pushappmgmt.PushApplicationDAO.changePushApplicationCredentials(String, String, String, String)
As of release 1.1, replaced by PushApplicationDAO.changePushApplicationPublicCredentials(String, String, String) for
updating the public credentials of a push application and
PushApplicationDAO.changePushApplicationEnterpriseCredentials(String, String, String, String) for updating the enterprise
credentials of a push application. |
|
| net.rim.pushsdk.pushappmgmt.PushAppMemoryDAOImpl.changePushApplicationCredentials(String, String, String, String)
|
|
| net.rim.pushsdk.pushappmgmt.PushAppRDBMSDAOImpl.changePushApplicationCredentials(String, String, String, String)
|
|
| net.rim.pushsdk.pushappmgmt.PushApplicationService.changePushApplicationCredentials(String, String, String, String, String, String)
As of release 1.1, replaced by PushApplicationService.changePushApplicationPublicCredentials(String, String, String, String)
for updating the public credentials of a push application and
PushApplicationService.changePushApplicationEnterpriseCredentials(String, String, String, String, String, String) for
updating the enterprise credentials of a push application. |
|
| net.rim.pushsdk.pushappmgmt.PushApplicationServiceImpl.changePushApplicationCredentials(String, String, String, String, String, String)
|
|
| net.rim.pushsdk.push.request.PushRequestDAO.findByStatusCode(StatusCode)
As of release 1.1, the StatusCode associated with the PushRequest is no longer
supported since the push may be sent to both the public/BIS and enterprise/BES PPG simultaneously. Please refer
to the PushRequestDetail records for the push to find out the status for each subscriber instead. |
|
| net.rim.pushsdk.push.request.PushRequestMemoryDAOImpl.findByStatusCode(StatusCode)
|
|
| net.rim.pushsdk.push.request.PushRequestRDBMSDAOImpl.findByStatusCode(StatusCode)
|
|
| net.rim.pushsdk.push.request.PushRequestService.findByStatusCode(StatusCode)
As of release 1.1, the StatusCode associated with the PushRequest is no longer
supported since the push may be sent to both the public/BIS and enterprise/BES PPG simultaneously. Please refer
to the PushRequestDetail records for the push to find out the status for each subscriber instead. |
|
| net.rim.pushsdk.push.request.PushRequestServiceImpl.findByStatusCode(StatusCode)
|
|
| net.rim.pushsdk.pap.control.CancelMessageControl.getAddresses()
As of release 1.1, replaced by CancelMessageControl.getAddressList(). |
|
| net.rim.pushsdk.pap.control.PushMessageControl.getAddresses()
As of release 1.1, replaced by PushMessageControl.getAddressList(). |
|
| net.rim.pushsdk.pap.control.StatusQueryMessageControl.getAddresses()
As of release 1.1, replaced by StatusQueryMessageControl.getAddressList(). |
|
| net.rim.pushsdk.pap.unmarshal.CancelResult.getAddresses()
As of release 1.1, replaced by CancelResult.getAddressList(). |
|
| net.rim.pushsdk.pap.unmarshal.StatusQueryResult.getAddresses()
As of release 1.1, replaced by StatusQueryResult.getAddressList(). |
|
| net.rim.pushsdk.subscription.SubMemoryDAOImpl.getConsecutiveFailedPushCount(SubscriberPartial)
|
|
| net.rim.pushsdk.subscription.SubRDBMSDAOImpl.getConsecutiveFailedPushCount(SubscriberPartial)
|
|
| net.rim.pushsdk.subscription.SubscriptionDAO.getConsecutiveFailedPushCount(SubscriberPartial)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionService.getConsecutiveFailedPushCount(SubscriberPartial)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.getConsecutiveFailedPushCount(SubscriberPartial)
|
|
| net.rim.pushsdk.pushappmgmt.PushApplication.getConsecutiveFailedPushThreshold()
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.push.request.PushRequest.getNotifyUrl()
As of version 1.1, use PushRequest.getPublicNotifyUrl() or PushRequest.getEnterpriseNotifyUrl() |
|
| net.rim.pushsdk.pushappmgmt.PushApplication.getNotifyUrl()
As of version 1.1, use PushApplication.getPublicNotifyUrl() or PushApplication.getEnterpriseNotifyUrl() |
|
| net.rim.pushsdk.pushappmgmt.PushApplication.getPassword()
As of release 1.1, use PushApplication.getPublicPassword() or PushApplication.getEnterprisePassword() |
|
| net.rim.pushsdk.commons.PushSDKProperties.getPpgAddress()
As of release 1.1, replaced by PushSDKProperties.getPublicPpgAddress() or PushSDKProperties.getEnterprisePpgAddress(). |
|
| net.rim.pushsdk.commons.PushSDKPropertiesImpl.getPpgAddress()
|
|
| net.rim.pushsdk.push.request.PushRequest.getStatusCode()
As of release 1.1, the status code of the PushRequest is no longer used. Since the
PushRequest may have been sent to both the public/BIS PPG and the enterprise/BES PPG the status of
the overall push is ambiguous. Instead, look at the status code in the PushRequestDetail for each
subscriber. |
|
| net.rim.pushsdk.push.request.PushRequest.getStatusDesc()
As of release 1.1, the status code of the PushRequest is no longer used. Since the
PushRequest may have been sent to both the public/BIS PPG and the enterprise/BES PPG the status of
the overall push is ambiguous. Instead, look at the status code in the PushRequestDetail for each
subscriber. |
|
| net.rim.pushsdk.subscription.SubMemoryDAOImpl.incrementConsecutiveFailedPushCount(String, String)
|
|
| net.rim.pushsdk.subscription.SubRDBMSDAOImpl.incrementConsecutiveFailedPushCount(String, String)
|
|
| net.rim.pushsdk.subscription.SubscriptionDAO.incrementConsecutiveFailedPushCount(String, String)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionService.incrementConsecutiveFailedPushCount(String, String)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.incrementConsecutiveFailedPushCount(String, String)
|
|
| net.rim.pushsdk.push.PushOutcome.isApplicationReliable()
As of release 1.1, replaced by PushOutcome.isAppReliable(). |
|
| net.rim.pushsdk.pushappmgmt.PushApplication.isDeprecatedConstructorUsed()
|
|
| net.rim.pushsdk.commons.PushSDKProperties.isUsingPublicPush()
As of release 1.1, replaced by PapControl.isUsingPublicPush() if using the
low-level PAP APIs, and PushApplication.getType() or
SubscriberPartial.getType() if using the high-level APIs. |
|
| net.rim.pushsdk.commons.PushSDKPropertiesImpl.isUsingPublicPush()
|
|
| net.rim.pushsdk.commons.PushSDKProperties.isUsingXmlParserDtdValidation()
As of release 1.1, DTD validation is not supported, and this method returns false. |
|
| net.rim.pushsdk.commons.PushSDKPropertiesImpl.isUsingXmlParserDtdValidation()
|
|
| net.rim.pushsdk.subscription.sync.SubSyncByAddressDAO.prepareFindByAppIdAndStatus(String, SubscriberStatus)
As of release 1.1, replaced by the SubSyncByAddressDAO.prepareFindByAppIdAndStatus(String, SubscriberStatus, int, int)
method instead. |
|
| net.rim.pushsdk.subscription.sync.SubSyncByAddressMemoryDAOImpl.prepareFindByAppIdAndStatus(String, SubscriberStatus)
|
|
| net.rim.pushsdk.subscription.sync.SubSyncByAddressRDBMSDAOImpl.prepareFindByAppIdAndStatus(String, SubscriberStatus)
|
|
| net.rim.pushsdk.subscription.sync.SubSyncByAddressDAO.prepareFindByAppIdAndStatusAndType(String, SubscriberStatus, SubscriberType)
As of release 1.1, replaced by the SubSyncByAddressDAO.prepareFindByAppIdAndStatusAndType(String, SubscriberStatus, SubscriberType, int, int) method instead. |
|
| net.rim.pushsdk.subscription.sync.SubSyncByAddressMemoryDAOImpl.prepareFindByAppIdAndStatusAndType(String, SubscriberStatus, SubscriberType)
|
|
| net.rim.pushsdk.subscription.sync.SubSyncByAddressRDBMSDAOImpl.prepareFindByAppIdAndStatusAndType(String, SubscriberStatus, SubscriberType)
|
|
| net.rim.pushsdk.pap.control.AddressList.print()
As of release 1.1, replaced by AddressList.print(boolean). |
|
| net.rim.pushsdk.subscription.SubMemoryDAOImpl.resetConsecutiveFailedPushCount(String, String)
|
|
| net.rim.pushsdk.subscription.SubRDBMSDAOImpl.resetConsecutiveFailedPushCount(String, String)
|
|
| net.rim.pushsdk.subscription.SubscriptionDAO.resetConsecutiveFailedPushCount(String, String)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionService.resetConsecutiveFailedPushCount(String, String)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.resetConsecutiveFailedPushCount(String, String)
|
|
| net.rim.pushsdk.pap.control.CancelMessageControl.setAddresses(AddressList)
As of release 1.1, replaced by CancelMessageControl.setAddressList(List). |
|
| net.rim.pushsdk.pap.control.PushMessageControl.setAddresses(AddressList)
As of release 1.1, replaced by PushMessageControl.setAddressList(List). |
|
| net.rim.pushsdk.pap.control.StatusQueryMessageControl.setAddresses(AddressList)
As of release 1.1, replaced by StatusQueryMessageControl.setAddressList(List). |
|
| net.rim.pushsdk.pap.unmarshal.CancelResult.setAddresses(AddressList)
As of release 1.1, replaced by CancelResult.setAddressList(List). |
|
| net.rim.pushsdk.pap.unmarshal.StatusQueryResult.setAddresses(AddressList)
As of release 1.1, replaced by StatusQueryResult.setAddressList(List). |
|
| net.rim.pushsdk.pushappmgmt.PushApplication.setConsecutiveFailedPushThreshold(Integer)
As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this count because the public/BIS PPG will be implementing this logic on the platform side instead. For enterprise/BES the push initiator must implement the logic if desired. |
|
| net.rim.pushsdk.push.request.PushRequest.setNotifyUrl(String)
As of version 1.1, use PushRequest.setPublicNotifyUrl(String) or PushRequest.setEnterpriseNotifyUrl(String) |
|
| net.rim.pushsdk.pushappmgmt.PushApplication.setNotifyUrl(String)
As of version 1.1, use PushApplication.setPublicNotifyUrl(String) or PushApplication.setEnterpriseNotifyUrl(String) |
|
| net.rim.pushsdk.pushappmgmt.PushApplication.setPassword(String)
As of release 1.1, use PushApplication.setPublicPassword(String) or PushApplication.setEnterprisePassword(String) |
|
| net.rim.pushsdk.commons.PushSDKProperties.setPpgAddress(String)
As of release 1.1, replaced by PushSDKProperties.setPublicPpgAddress(String) or PushSDKProperties.setEnterprisePpgAddress(String)
. |
|
| net.rim.pushsdk.commons.PushSDKPropertiesImpl.setPpgAddress(String)
|
|
| net.rim.pushsdk.pap.control.AddressList.setPushSDKProperties(PushSDKProperties)
As of release 1.1, replaced by AddressList.print(boolean) and AddressList.validate(boolean, boolean) for indicating
whether this address list applies to a public (BIS) operation or an enterprise (BES) operation. |
|
| net.rim.pushsdk.pushappmgmt.PushApplicationDAO.setPushSDKProperties(PushSDKProperties)
This setter was added in 1.1, but is deprecated, since it is used only to support backwards compatibility. |
|
| net.rim.pushsdk.pushappmgmt.PushAppMemoryDAOImpl.setPushSDKProperties(PushSDKProperties)
|
|
| net.rim.pushsdk.pushappmgmt.PushAppRDBMSDAOImpl.setPushSDKProperties(PushSDKProperties)
|
|
| net.rim.pushsdk.push.request.PushRequest.setStatusCode(StatusCode)
As of release 1.1, the status code of the PushRequest is no longer used. Since the
PushRequest may have been sent to both the public/BIS PPG and the enterprise/BES PPG the status of
the overall push is ambiguous. Instead, look at the status code in the PushRequestDetail for each
subscriber. |
|
| net.rim.pushsdk.push.request.PushRequest.setStatusDesc(String)
As of release 1.1, the status code of the PushRequest is no longer used. Since the
PushRequest may have been sent to both the public/BIS PPG and the enterprise/BES PPG the status of
the overall push is ambiguous. Instead, look at the status code in the PushRequestDetail for each
subscriber. |
|
| net.rim.pushsdk.commons.PushSDKProperties.setUsingPublicPush(boolean)
As of release 1.1, replaced by PapControl.setUsingPublicPush(boolean) if
using the low-level PAP APIs, and
PushApplication.setType(net.rim.pushsdk.pushappmgmt.PushApplicationType) or
SubscriberPartial.setType(net.rim.pushsdk.subscription.SubscriberType) if
using the high-level APIs. |
|
| net.rim.pushsdk.commons.PushSDKPropertiesImpl.setUsingPublicPush(boolean)
|
|
| net.rim.pushsdk.commons.PushSDKProperties.setUsingXmlParserDtdValidation(boolean)
As of release 1.1, DTD validation is not supported, and this method has no effect. |
|
| net.rim.pushsdk.commons.PushSDKPropertiesImpl.setUsingXmlParserDtdValidation(boolean)
|
|
| net.rim.pushsdk.subscription.SubscriptionService.syncSubscribersWithPPG(String, String)
As of release 1.1, replaced by the SubscriptionService.syncSubscribersWithPPGForStatus(String, SubscriberStatus, int, int, String)
method instead. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.syncSubscribersWithPPG(String, String)
|
|
| net.rim.pushsdk.subscription.SubscriptionService.syncSubscribersWithPPGByStatus(String, SubscriberStatus, String)
As of release 1.1, replaced by the SubscriptionService.syncSubscribersWithPPGForStatus(String, SubscriberStatus, int, int, String)
method instead. |
|
| net.rim.pushsdk.subscription.SubscriptionServiceImpl.syncSubscribersWithPPGByStatus(String, SubscriberStatus, String)
|
|
| net.rim.pushsdk.push.request.PushRequestDAO.updatePushRequest(PushRequest)
As of release 1.1, the StatusCode associated with the PushRequest is no longer
supported since the push may be sent to both the public/BIS and enterprise/BES PPG simultaneously. Please refer
to the PushRequestDetail records for the push to find out the status for each subscriber instead. |
|
| net.rim.pushsdk.push.request.PushRequestMemoryDAOImpl.updatePushRequest(PushRequest)
|
|
| net.rim.pushsdk.push.request.PushRequestRDBMSDAOImpl.updatePushRequest(PushRequest)
|
|
| net.rim.pushsdk.push.request.PushRequestService.updatePushRequest(PushRequest)
As of release 1.1, the StatusCode associated with the PushRequest is no longer
supported since the push may be sent to both the public/BIS and enterprise/BES PPG simultaneously. Please refer
to the PushRequestDetail records for the push to find out the status for each subscriber instead. |
|
| net.rim.pushsdk.push.request.PushRequestServiceImpl.updatePushRequest(PushRequest)
|
|
| net.rim.pushsdk.pap.control.AddressList.validate()
As of release 1.1, replaced by AddressList.validate(boolean, boolean). |
|
| net.rim.pushsdk.pap.control.AddressList.validate(boolean)
As of release 1.1, replaced by AddressList.validate(boolean, boolean). |
|
| net.rim.pushsdk.push.PushParameters.validate(boolean)
As of release 1.1, replaced by PushParameters.validate(PushApplicationType) |
|
| Deprecated Constructors | |
|---|---|
| net.rim.pushsdk.pap.control.CancelMessageControl()
As of release 1.1, replaced by CancelMessageControl.CancelMessageControl(boolean) constructor instead. To use this
constructor, you must configure the SDK to be in public or enterprise mode through the PushSDK.properties file
by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.CancelMessageControl(String)
As of release 1.1, replaced by CancelMessageControl.CancelMessageControl(boolean, String) constructor instead. To use this
constructor, you must configure the SDK to be in public or enterprise mode through the PushSDK.properties file
by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.CancelMessageControl(String, List As of release 1.1, replaced by CancelMessageControl.CancelMessageControl(boolean, String, List) constructor instead. To use
this constructor, you must configure the SDK to be in public or enterprise mode through the PushSDK.properties
file by setting the use.public.push flag. |
|
| net.rim.pushsdk.pushappmgmt.PushApplication()
As of release 1.1, use PushApplication.PushApplication(PushApplicationType) |
|
| net.rim.pushsdk.pap.control.PushMessageControl()
As of release 1.1, replaced by the PushMessageControl.PushMessageControl(boolean) constructor instead. To use this
constructor, you must configure the SDK to be in public or enterprise mode through the PushSDK.properties file
by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.PushMessageControl(IdGenerator, String)
As of release 1.1, replaced by the PushMessageControl.PushMessageControl(boolean, IdGenerator, String) constructor
instead. To use this constructor, you must configure the SDK to be in public or enterprise mode through the
PushSDK.properties file by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.PushMessageControl(IdGenerator, String, List As of release 1.1, replaced by the PushMessageControl.PushMessageControl(boolean, IdGenerator, String, List) constructor
instead. To use this constructor, you must configure the SDK to be in public or enterprise mode through the
PushSDK.properties file by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.PushMessageControl(IdGenerator, String, String)
As of release 1.1, replaced by the PushMessageControl.PushMessageControl(boolean, IdGenerator, String, String)
constructor instead. To use this constructor, you must configure the SDK to be in public or enterprise mode
through the PushSDK.properties file by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.PushMessageControl(IdGenerator, String, String, List As of release 1.1, replaced by the PushMessageControl.PushMessageControl(boolean, IdGenerator, String, String, List)
constructor instead. To use this constructor, you must configure the SDK to be in public or enterprise mode
through the PushSDK.properties file by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.StatusQueryMessageControl()
As of release 1.1, replaced by the StatusQueryMessageControl.StatusQueryMessageControl(boolean) constructor instead. To use this
constructor, you must configure the SDK to be in public or enterprise mode through the PushSDK.properties file
by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.StatusQueryMessageControl(String)
As of release 1.1, replaced by the StatusQueryMessageControl.StatusQueryMessageControl(boolean, String) constructor instead. To
use this constructor, you must configure the SDK to be in public or enterprise mode through the
PushSDK.properties file by setting the use.public.push flag. |
|
| net.rim.pushsdk.pap.control.StatusQueryMessageControl(String, List As of release 1.1, replaced by the StatusQueryMessageControl.StatusQueryMessageControl(boolean, String, List) constructor
instead. To use this constructor, you must configure the SDK to be in public or enterprise mode through the
PushSDK.properties file by setting the use.public.push flag. |
|
| net.rim.pushsdk.subscription.web.SubscribeRequest(String, String, String, String, String)
As of release 1.1, replaced by the SubscribeRequest.SubscribeRequest(String, String, String, String, String, SubscriberType) constructor instead. To use
this constructor, you must configure the SDK to be in public or enterprise mode through the PushSDK.properties
file by setting the use.public.push flag. |
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||