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 usingSavedPaymentMethodto 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 usingSavedPaymentMethodto 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=falsesince 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.since 1.0.2, in favor of usingSavedPaymentMethodto manage saved payment methods.since 1.0.2, in favor of usingSavedPaymentMethodSummaryto 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
CreateSavedPaymentMethodEventListenersince 1.0.2, in favor of using PaymentTransactionServices to manage saved payment methods.
-
Deprecated ClassesClassDescriptionsince 1.0.2, in favor of using
SavedPaymentMethodto 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 usingSavedPaymentMethodto manage saved payment methods.in favor ofCheckoutRollbackEventListenersince 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=falsesince 1.0.2, in favor of usingSavedPaymentMethodto manage saved payment methods.since 1.0.2, in favor of usingSavedPaymentMethodSummaryto 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 Enum ClassesEnum ClassDescriptionsince 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 InterfacesAnnotation InterfaceDescriptionsince 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.shouldSavePaymentForFutureUseto support owning user types other than a customer (i.e. account).in favor ofPaymentTransaction.nextActionsince 1.0.2, in favor ofJpaPayment.shouldSavePaymentForFutureUseto support owning user types other than a customer (i.e. account).since 1.0.2, in favor ofJpaPayment.shouldSavePaymentForFutureUseto 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.shouldSavePaymentForFutureUseto 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).in favor ofTransactionExecutionDetail.nextActionsince 1.0.2, in favor ofUpdatePaymentRequest.shouldSavePaymentForFutureUse()to support owning user types other than a customer (i.e. account).