Deprecated API

Contents

• For Removal
• Interfaces
• Classes
• Annotation Types
• Methods

For Removal

Element	Description
com.broadleafcommerce.customer.domain.PaymentAccount	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.domain.PaymentAccountSummary	since 1.7.2, in favor of using SavedPaymentMethodSummary in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.messaging.autoconfigure.CreatePaymentAccountEventProperties	since 1.7.2, use PaymentAccount.getDisplayAttributes() instead
com.broadleafcommerce.customer.messaging.CreatePaymentAccountEventListener	since 1.7.2. The creation of saved payment methods as a portion of the checkout process is now handled via a post-transaction hook in PaymentTransactionServices. If the saved payment method storage location is BLC_CUSTOMER_SERVICES, then this listener should be enabled for a time to handle any existing messages whose saved payment methods were not created via the PaymentTransactionServices hook. Once a day or two have passed after adopting the PaymentTransactionServices changes, this listener can be disabled.
com.broadleafcommerce.customer.messaging.CustomerCheckoutCompletionConsumer	since 1.7.2, saved payments should be handled by PaymentTransactionServices, therefore this should not be needed
com.broadleafcommerce.customer.provider.jpa.domain.JpaPaymentAccount	since 1.7.2, in favor of using JpaSavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.provider.jpa.repository.JpaPaymentAccountRepository	since 1.7.2, in favor of using JpaSavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.repository.PaymentAccountRepository	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.anonymization.PaymentAccountAnonymizationHandler	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods, therefore this endpoint should not be needed.
com.broadleafcommerce.customer.service.autoconfigure.ConditionalOnCustomerAsSavedPaymentStorageLocation	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.autoconfigure.CustomerServiceAutoConfiguration.SavedPaymentAccountConfiguration	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.DefaultPaymentAccountService	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.PaymentAccountService	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.provider.domain.Payment	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.domain.Payment.getShouldSavePaymentToCustomer()	since 1.7.2, in favor of Payment.getShouldSavePaymentForFutureUse() to support owning user types other than a customer (i.e. account).
com.broadleafcommerce.customer.service.provider.domain.PaymentTransaction	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.external.ExternalPaymentProperties	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.external.ExternalPaymentProvider	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.PaymentProvider	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.summary.DefaultPaymentAccountSummaryService	since 1.7.2, in favor of using SavedPaymentMethodSummary in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.summary.PaymentAccountSummaryService	since 1.7.2, in favor of using SavedPaymentMethodSummary in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.validation.DefaultPaymentAccountValidator	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.web.autoconfigure.CustomerWebSecurityAutoConfiguration.LegacySavedPaymentMethodSecurityConfiguration	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.web.endpoint.CustomerPaymentAccountEndpoint	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.web.endpoint.SensitiveCustomerPaymentAccountEndpoint	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.

Interfaces

Interface	Description
com.broadleafcommerce.customer.messaging.CustomerCheckoutCompletionConsumer	since 1.7.2, saved payments should be handled by PaymentTransactionServices, therefore this should not be needed
com.broadleafcommerce.customer.provider.jpa.repository.JpaPaymentAccountRepository	since 1.7.2, in favor of using JpaSavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.repository.PaymentAccountRepository	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.PaymentAccountService	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.provider.PaymentProvider	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.summary.PaymentAccountSummaryService	since 1.7.2, in favor of using SavedPaymentMethodSummary in PaymentTransactionServices to manage saved payment methods.

Classes

Class	Description
com.broadleafcommerce.customer.domain.PaymentAccount	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.domain.PaymentAccountSummary	since 1.7.2, in favor of using SavedPaymentMethodSummary in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.messaging.autoconfigure.CreatePaymentAccountEventProperties	since 1.7.2, use PaymentAccount.getDisplayAttributes() instead
com.broadleafcommerce.customer.messaging.CreatePaymentAccountEventListener	since 1.7.2. The creation of saved payment methods as a portion of the checkout process is now handled via a post-transaction hook in PaymentTransactionServices. If the saved payment method storage location is BLC_CUSTOMER_SERVICES, then this listener should be enabled for a time to handle any existing messages whose saved payment methods were not created via the PaymentTransactionServices hook. Once a day or two have passed after adopting the PaymentTransactionServices changes, this listener can be disabled.
com.broadleafcommerce.customer.provider.jpa.domain.JpaPaymentAccount	since 1.7.2, in favor of using JpaSavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.anonymization.PaymentAccountAnonymizationHandler	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods, therefore this endpoint should not be needed.
com.broadleafcommerce.customer.service.autoconfigure.CustomerServiceAutoConfiguration.SavedPaymentAccountConfiguration	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.DefaultPaymentAccountService	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.provider.domain.Payment	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.domain.PaymentTransaction	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.external.ExternalPaymentProperties	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.provider.external.ExternalPaymentProvider	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
com.broadleafcommerce.customer.service.summary.DefaultPaymentAccountSummaryService	since 1.7.2, in favor of using SavedPaymentMethodSummary in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.validation.DefaultPaymentAccountValidator	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.web.autoconfigure.CustomerWebSecurityAutoConfiguration.LegacySavedPaymentMethodSecurityConfiguration	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.web.endpoint.CustomerPaymentAccountEndpoint	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.web.endpoint.SensitiveCustomerPaymentAccountEndpoint	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.

Annotation Types

Annotation Type	Description
com.broadleafcommerce.customer.service.autoconfigure.ConditionalOnCustomerAsSavedPaymentStorageLocation	since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.

Methods

Method	Description
com.broadleafcommerce.customer.domain.AccountMember.getAdditionalPhones()	Use the customer's additional phones instead
com.broadleafcommerce.customer.domain.AccountMember.setAdditionalPhones(List<AdditionalPhone>)	Use the customer's additional phones instead
com.broadleafcommerce.customer.domain.Customer.getDefaultPaymentAccountId()	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.domain.Customer.setDefaultPaymentAccountId(String)	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.provider.jpa.domain.JpaCustomer.getDefaultPaymentAccountId()	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.provider.jpa.domain.JpaCustomer.setDefaultPaymentAccountId(String)	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods.
com.broadleafcommerce.customer.service.anonymization.CustomerAnonymizationProperties.isPaymentAccountEnabled()	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods
com.broadleafcommerce.customer.service.anonymization.CustomerAnonymizationProperties.setPaymentAccountEnabled(boolean)	since 1.7.2, in favor of using SavedPaymentMethod in PaymentTransactionServices to manage saved payment methods
com.broadleafcommerce.customer.service.provider.domain.Payment.getShouldSavePaymentToCustomer()	since 1.7.2, in favor of Payment.getShouldSavePaymentForFutureUse() to support owning user types other than a customer (i.e. account).
com.broadleafcommerce.customer.service.provider.domain.Payment.setShouldSavePaymentToCustomer(boolean)	since 1.7.2, in favor of Payment.shouldSavePaymentForFutureUse to support owning user types other than a customer (i.e. account).
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.getAdditionalPhones()	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.getEmail()	We use the customer's email instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.getFirstName()	We use the customer's name instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.getLastName()	We use the customer's name instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.getPhone()	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.getUsername()	We use the customer's username instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setAdditionalPhones(List<AdditionalPhone>)	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setEmail(String)	We use the customer's email instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setFirstName(String)	We use the customer's name instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setLastName(String)	We use the customer's name instead.
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setPhone(Phone)	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setUsername(String)	We use the customer's username instead.
com.broadleafcommerce.customer.web.endpoint.domain.UpdateAccountMemberRequest.getAdditionalPhones()	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.UpdateAccountMemberRequest.getEmail()	We use the customer's email instead.
com.broadleafcommerce.customer.web.endpoint.domain.UpdateAccountMemberRequest.getPhone()	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.UpdateAccountMemberRequest.setAdditionalPhones(List<AdditionalPhone>)	Use the customer's phone numbers instead
com.broadleafcommerce.customer.web.endpoint.domain.UpdateAccountMemberRequest.setEmail(String)	We use the customer's email instead.
com.broadleafcommerce.customer.web.endpoint.domain.UpdateAccountMemberRequest.setPhone(Phone)	Use the customer's phone numbers instead