To completely override an existing bean definition in your webapp extension, in your webapp JAR extension's plugin.xml, you define a new bean with the exact same bean id as the bean you are overriding.

For example, suppose you want to override the cartFormBeanFactory bean in ep-storefront\src\main\resources\spring\service\serviceSF.xml:

                  storefront/ep-storefront/src/main/resources/spring/service/serviceSF.xml
	<bean id="cartFormBeanFactoryTemplate" abstract="true"
		class="com.elasticpath.sfweb.controller.impl.ShoppingItemFormBeanContainerFactoryImpl" >
        <property name="productSkuLookup" ref="productSkuLookup" />
        <property name="productViewService" ref="productViewService" />
		<property name="storeProductService" ref="storeProductService" />
        <property name="priceLookupFacade" ref="priceLookupFacade" />
        <property name="jsonBundleFactory" ref="jsonBundleFactory"/commerce-legacy/>
        <property name="jsonBundleService" ref="jsonBundleService"/commerce-legacy/>
		<property name="loadProductAssociations" value="true"/commerce-legacy/>
		<property name="beanFactory" ref="coreBeanFactory" />
	 	<property name="shoppingItemAssembler" ref="shoppingItemAssembler" />
	 	<property name="cartDirector" ref="cartDirector" />
		<property name="cartDirectorService" ref="cartDirectorService" />
	 	<property name="requestHelper" ref="requestHelper"/commerce-legacy/>
	</bean>

	<bean id="cartFormBeanFactory" parent="cartFormBeanFactoryTemplate" />

               

In your storefront JAR extension's ep-storefront-plugin.xml, you would add the following:

<bean id="cartFormBeanFactory" parent="cartFormBeanFactoryTemplate"
    class="com.extensions.tshirt.sfweb.controller.impl.ExtShoppingItemFormBeanContainerFactoryImpl">

However, you may want to change only the configuration parameters of an existing bean definition, or override just the implementation class. There is a way to so this without replacing the entire bean definition. To do this, you need to use the PluginBeanFactoryPostProcessor.

The com.elasticpath.commons.util.impl.PluginBeanFactoryPostProcessor class is an implementation of the Spring BeanFactoryPostProcessor interface. Spring invokes this after all of the configuration has been discovered and loaded in memory, but before the actual objects are created.

Below is a PluginBeanFactoryPostProcessor bean definition:

<bean class="com.elasticpath.commons.util.impl.PluginBeanFactoryPostProcessor">
  <property name="extensionBeanName">
    <value>EXTENSION_BEAN_NAME</value>
  </property>
  <property name="extensionClassName">
    <value>EXTENSION_CLASS_NAME</value>
  </property>
  <property name="propertyName">
    <value>PROPERTY_NAME</value>
  </property>
  <property name="propertyValue">
    <ref bean="PROPERTY_VALUE"/commerce-legacy/>
  </property>
</bean>

To override or extend an existing built-in bean, add a PluginBeanFactoryPostProcessor bean definition in your webapp JAR extension's plugin.xml and specify the following properties:

For example, suppose the default configuration contains the following bean definition:

<bean id="authenticationProcessingFilter"
      class="com.elasticpath.sfweb.filters.EpAuthenticationProcessingFilter">
  <property name="webCustomerSessionService">
    <ref bean="webCustomerSessionService"/commerce-legacy/>
  </property>
  <property name="authenticationManager">
    <ref bean="authenticationManager"/commerce-legacy/>
  </property>
  <property name="authenticationFailureUrl">
    <value>/sign-in.ep?login_failed=1</value>
  </property>
  <property name="defaultTargetUrl">
    <value>/manage-account.ep</value>
  </property>
  <property name="filterProcessesUrl">
    <value>/j_acegi_security_check.ep</value>
  </property>
</bean>

The following bean definition can be included in a plugin.xml file to override the original bean definition of authenticationProcessingFilter:

<bean class="com.elasticpath.commons.util.impl.PluginBeanFactoryPostProcessor">
  <property name="extensionBeanName">
    <value>authenticationProcessingFilter</value>
  </property>
  <property name="extensionClassName">
    <value>com.elasticpath.plugins.custom_authenticator.filters.CustomAuthenticationProcessingFilter</value>
  </property>
  <property name="propertyName">
    <value>customerService</value>
  <property name="propertyValue">
    <ref bean="customerService"/commerce-legacy/>
  </property>
</bean>

In this example, the default EpAuthenticationProcessingFilter implementation is replaced by CustomAuthenticationProcessingFilter, which includes a new property named customerService.

To override multiple properties on a particular bean, use the propertiesMap property as follows:

<property name="propertiesMap">
  <map>
    <entry key="customerService">
      <ref bean="customerService"/commerce-legacy/>
    </entry>
    <entry key="elasticPath">
      <ref bean="elasticPath"/commerce-legacy/>
    </entry>
  </map>
</property>