Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionsince 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore these properties will no longer be needed.since 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore these properties will no longer be needed.since 1.0.2, in favor of
Payment.getShouldSavePaymentForFutureUse()
to support owning user types other than a customer (i.e. account).due to removal of usages in the frameworksince 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore this annotation will no longer be needed.since 1.0.2, in favor of usingSavedPaymentMethod
to manage saved payment methods.since 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore these properties will no longer be needed.since 1.0.2, in favor of usingSavedPaymentMethod
to manage saved payment methods.no longer usedsince 1.0.2, The creation of saved payment methods as a portion of the checkout process is now handled via a post-transaction hook inTransactionExecutionService
. Once a day or two have passed after adopting the upgrade, this listener can be disabled by declaringbroadleaf.paymenttransaction.saved-payment.checkout-complete-create-listener.enabled=false
since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.since 1.0.2, in favor of usingSavedPaymentMethod
to manage saved payment methods.since 1.0.2, in favor of usingSavedPaymentMethodSummary
to manage saved payment methods.since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.this method is not used anymoresince 1.0.2, in favor ofCreatePaymentRequest.shouldSavePaymentForFutureUse()
to support owning user types other than a customer (i.e. account).since 1.0.2, in favor ofUpdatePaymentRequest.shouldSavePaymentForFutureUse()
to support owning user types other than a customer (i.e. account).since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.
-
Deprecated InterfacesInterfaceDescriptionsince 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore these properties will no longer be needed.since 1.0.2, see
CreateSavedPaymentMethodEventListener
since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.
-
Deprecated ClassesClassDescriptionsince 1.0.2, in favor of using
SavedPaymentMethod
to manage saved payment methods.since 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore these properties will no longer be needed.since 1.0.2, in favor of usingSavedPaymentMethod
to manage saved payment methods.in favor ofCheckoutRollbackEventListener
since 1.0.2, The creation of saved payment methods as a portion of the checkout process is now handled via a post-transaction hook inTransactionExecutionService
. Once a day or two have passed after adopting the upgrade, this listener can be disabled by declaringbroadleaf.paymenttransaction.saved-payment.checkout-complete-create-listener.enabled=false
since 1.0.2, in favor of usingSavedPaymentMethod
to manage saved payment methods.since 1.0.2, in favor of usingSavedPaymentMethodSummary
to manage saved payment methods.since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.since 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.
-
Deprecated EnumsEnumDescriptionsince 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore these properties will no longer be needed.
-
Deprecated ExceptionsExceptionsDescriptiondue to removal of usages in the framework
-
Deprecated Annotation TypesAnnotation TypeDescriptionsince 1.0.2. In the future, the option of using CustomerServices as saved payment method storage location will be removed, therefore this annotation will no longer be needed.
-
Deprecated MethodsMethodDescriptionsince 1.0.2, use
Payment.getOwningUserType()
andPayment.getOwningUserId()
insteadsince 1.0.2, in favor ofPayment.getShouldSavePaymentForFutureUse()
to support owning user types other than a customer (i.e. account).since 1.0.2, usePayment.getOwningUserType()
andPayment.getOwningUserId()
insteadsince 1.0.2, in favor ofPayment.shouldSavePaymentForFutureUse
to support owning user types other than a customer (i.e. account).since 1.0.2, in favor ofJpaPayment.shouldSavePaymentForFutureUse
to support owning user types other than a customer (i.e. account).since 1.0.2, in favor ofJpaPayment.shouldSavePaymentForFutureUse
to support owning user types other than a customer (i.e. account).no longer usedno longer usedsince 1.0.2, no longer usedthis method is not used anymoresince 1.0.2, in favor ofCreatePaymentRequest.shouldSavePaymentForFutureUse
to support owning user types other than a customer (i.e. account).since 1.0.2, in favor ofCreatePaymentRequest.shouldSavePaymentForFutureUse()
to support owning user types other than a customer (i.e. account).since 1.0.2, in favor ofUpdatePaymentRequest.shouldSavePaymentForFutureUse()
to support owning user types other than a customer (i.e. account).