从5.6迁移到6.7 | HMC Config Migrator实用程序不起作用

2020-09-20 08:58发布

点击此处---> 群内免费提供SAP练习系统(在群公告中)加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)专家们, 我正在尝试将Hybr...

         点击此处--->   EasySAP.com群内免费提供SAP练习系统(在群公告中)

加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)


专家们,

我正在尝试将Hybris System从v5.6升级到v6.7。 在使用 HMC Config Migrator Utility 为我的自定义扩展生成Backoffice配置时 例外。 当migrator实用程序仍在引用旧版本时," backoffice-widgets-6.7.0.0-RC8.jar"中的类和方法似乎已更改。 Hybris是否已推出v6.7的Config Migrator实用程序的升级版本? 如果没有,是否可以解决此问题?

异常日志-

java.lang.NoSuchMethodError:com.hybris.cockpitng.config.explorertree.jaxb.ExplorerTree.getNavigationNodeOrTypeNode()Ljava/util/List; 在de.hybris.hmc2.services.config.impl.DefaultHmc2TreeConfigurationHelper.createConfiguration(DefaultHmc2TreeConfigurationHelper.java:41)〜[?:?]在de.hybris.hmc2.services.config.impl.DefaultHmc2ConfigurationService.migrateHMCConfiguration(DefaultHmc2ConfigurationService.java: 101)在de.hybris.hmc2.services.config.Hmc2ConfigurationService $ migrateHMCConfiguration.call(未知源)处的[[?:?]〜[?:?]在HmcConfigMigratorWidgetController.migrateSelected(script152595221967594242828006.groovy:382)处的[?:?]〜[?:? ]在sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)〜[?:1.8.0_60]在sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)〜[?:1.8.0_60]在sun.reflect.DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:43)〜[?:1.8.0_60] at java.lang.reflect.Method.invoke(Method.java:497)〜[?:1.8.0_60] at com.hybris.cockpitng.util .ViewAnnotationAwareComposer.invokeListenerMethod(ViewAnnotationAwareComposer.java:107)〜[cockpitframework-6.7.0.0-RC8.jar :?]在c om.hybris.cockpitng.util.DefaultWidgetController.invokeListenerMethod(DefaultWidgetController.java:178)〜[cockpitframework-6.7.0.0-RC8.jar :?] at com.hybris.cockpitng.util.ViewAnnotationAwareComposer.lambda $ applyEventListener $ 0(ViewAnnotationAwareComposer java:124)〜[cockpitframework-6.7.0.0-RC8.jar :?]在org.zkoss.zk.ui.AbstractComponent.onEvent(AbstractComponent.java:3162)〜[zk-8.5.0.jar:3.6.4 ]在org.zkoss.zk.ui.AbstractComponent.service(AbstractComponent.java:3132)〜[zk-8.5.0.jar:3.6.4]在org.zkoss.zk.ui.AbstractComponent.service(AbstractComponent.java :3074)〜[zk-8.5.0.jar:3.6.4],位于org.zkoss.zk.ui.impl.EventProcessor.process(EventProcessor.java:138)〜[zk-8.5.0.jar:3.6。 4] at org.zkoss.zk.ui.impl.UiEngineImpl.processEvent(UiEngineImpl.java:1846)〜[zk-8.5.0.jar:3.6.4] at org.zkoss.zk.ui.impl.UiEngineImpl。 org.zkoss.zk.ui.impl.UiEngineImpl.execUpdate(UiEngineImpl.java:1321)处的进程(UiEngineImpl.java:1618)[zk-8.5.0.jar:3.6.4] [zk-8.5.0.jar :3.6.4],网址为org.zkoss.zk.au.http.DHtmlUpdateS ervlet.process(DHtmlUpdateServlet.java:606)[zk-8.5.0.jar:3.6.4] at org.zkoss.zk.au.http.DHtmlUpdateServlet.doGet(DHtmlUpdateServlet.java:482)[zk-8.5.0 org.zkoss.zk.au.http.DHtmlUpdateServlet.doPost(DHtmlUpdateServlet.java:490)的.jar:3.6.4] [java.servlet.http.HttpServlet的[zk-8.5.0.jar:3.6.4]]。 service(HttpServlet.java:661)[servlet-api.jar :?]在javax.servlet.http.HttpServlet.service(HttpServlet.java:742)[servlet-api.jar :?]在org.apache.catalina org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)的core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)[catalina.jar:8.5.23] [catalina.jar:8.5.23] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)上的org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)[tomcat-websocket.jar:8.5.23] [catalina.jar:8.5.23],位于org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)[catalina。 jar:8.5.23]在org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:208)[spring-security-web-4.2.4.RELEASE.jar:4.2.4.RELEASE]在org.springframework .security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)[spring-security-web-4.2.4.RELEASE.jar:4.2.4.RELEASE]位于org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy .java:347)[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]

问候,马诺伊。