Question Re: No bean named 'assistedServicePathRestrictionEvaluator' available. When we add property setting in custom storefront local.properties for the assistedservicestorefront-web-spring.xml in CRM and CX Q&A

No bean named 'assistedServicePathRestrictionEvaluator' available. When we add property setting in custom storefront local.properties for the assistedservicestorefront-web-spring.xml

Former Member — Mon, 04 Feb 2019 19:08:45 GMT

Added this property in customstore front .additionalWebSpringConfigs.assistedservicestorefront=classpath:/assistedservicestorefront/web/spring/assistedservicestorefront-web-spring.xml

Done this based on https://answers.sap.com/questions/12758476/asm-not-working-on-a-custom-storefront.html

[localhost-startStop-1] [ContextLoader] Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultStorefrontTenantDefaultFilterChainList': Post-processing of FactoryBean's singleton object failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'AssistedservicestorefrontFilterListMergeDirective' defined in class path resource [assistedservicestorefront/web/spring/assistedservicestorefront-web-spring.xml]: Cannot resolve reference to bean 'assistedServiceFilter' while setting add; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'assistedServiceFilter' defined in class path resource [assistedservicestorefront/web/spring/assistedservicestorefront-web-spring.xml]: Cannot resolve reference to bean 'assistedServicePathRestrictionEvaluator' while setting bean property 'assistedServicePathRestrictionEvaluator'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'assistedServicePathRestrictionEvaluator' available at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:121) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1640) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:297) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) ~[spring-beans-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) ~[spring-context-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.context.support.AbstractApplicationContext.__refresh(AbstractApplicationContext.java:543) ~[spring-context-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:41010) ~[spring-context-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443) ~[spring-web-4.3.17.RELEASE.jar:4.3.17.RELEASE] at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325) [spring-web-4.3.17.RELEASE.jar:4.3.17.RELEASE] at de.hybris.platform.spring.HybrisContextLoaderListener.doInitWebApplicationContext(HybrisContextLoaderListener.java:225) [coreserver.jar:?] at de.hybris.platform.spring.HybrisContextLoaderListener.initWebApplicationContext(HybrisContextLoaderListener.java:199) [coreserver.jar:?] at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107) [spring-web-4.3.17.RELEASE.jar:4.3.17.RELEASE] at de.hybris.platform.spring.HybrisContextLoaderListener.contextInitialized(HybrisContextLoaderListener.java:95) [coreserver.jar:?] at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4745) [catalina.jar:8.5.23] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207) [catalina.jar:8.5.23] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:8.5.23] at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1419) [catalina.jar:8.5.23] at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1409) [catalina.jar:8.5.23] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_181] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]

Re: No bean named 'assistedServicePathRestrictionEvaluator' available. When we add property setting in custom storefront local.properties for the assistedservicestorefront-web-spring.xml

arvind-kumar_avinash — Mon, 04 Feb 2019 19:54:21 GMT

Hi - it seems there is some confusion regarding addoninstall command. First of all, let's talk about your statement:

Added this property in customstore front .additionalWebSpringConfigs.assistedservicestorefront=classpath:/assistedservicestorefront/web/spring/assistedservicestorefront-web-spring.xml

Please note that this property is not added in the project.properties file of the storefront; rather, it is added in the project.properties file of the addon.

Second, you do not have to do it manually; the addoninstall command does it for you. Please go through the following extract from https://help.hybris.com/1811/hcd/8adf7365866910149ceb975f778d809d.html carefully:

So, all you need to do is to install the assistedservicestorefront AddOn again if something went wrong in your previous attempt.

Note that apart from generating the relevant project.properties file for the AddOn, the addoninstall command also adds the AddOn to the extensioninfo.xml file of the storefront.

Therefore, there are two places you need to check after executing the addoninstall command:

The project.properties of the addon
The extensioninfo.xml of your storefront

Re: No bean named 'assistedServicePathRestrictionEvaluator' available. When we add property setting in custom storefront local.properties for the assistedservicestorefront-web-spring.xml

arvind-kumar_avinash — Thu, 14 Feb 2019 21:32:28 GMT

Hi - any update on this?

Re: No bean named 'assistedServicePathRestrictionEvaluator' available. When we add property setting in custom storefront local.properties for the assistedservicestorefront-web-spring.xml

Former Member — Fri, 29 Mar 2019 15:48:33 GMT

Any updates on this?We also usually added the property in custom storefront project.properties file, since the addon is not versioned and it was enough before. Not every dev needed to install the addon per say. But apparently it does not work for this addon.

Re: No bean named 'assistedServicePathRestrictionEvaluator' available. When we add property setting in custom storefront local.properties for the assistedservicestorefront-web-spring.xml

arvind-kumar_avinash — Sat, 30 Mar 2019 10:11:32 GMT

Hi - the recommended practice is to execute addoninstall to install the addon. I hope you have gone through my answer. However, I haven't heard anything from yet.