Foren

Is Liferay 6.1 API backward compatible with Liferay 6.0

thumbnail
Nilesh Gundecha, geändert vor 12 Jahren.

Is Liferay 6.1 API backward compatible with Liferay 6.0

Regular Member Beiträge: 205 Beitrittsdatum: 01.12.09 Neueste Beiträge
Friends,

I have developed plugin project for Liferay 6.0.6. With the release of Liferay 6.1, I plan to run this plugin on Liferay 6.1.

Is Liferay 6.1 API backward compatible with Liferay 6.0.6?

I tried deploying my plugin project and got exception from Spring framework as below -

07:01:59,454 ERROR [PortletApplicationContext:87] org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [com.liferay.portal.sp
ring.annotation.BeanReferenceAnnotationBeanPostProcessor] not found
Offending resource: ServletContext resource [/WEB-INF/classes/META-INF/base-spring.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostPro
cessor] not found
Offending resource: ServletContext resource [/WEB-INF/classes/META-INF/base-spring.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
        at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
        at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:291)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:491)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:396)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:365)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:258)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:153)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:132)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
        at com.liferay.portal.spring.context.PortletApplicationContext.loadBeanDefinitions(PortletApplicationContext.java:76)
        at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93)
        at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
        at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
        at com.liferay.portal.spring.context.PortletContextLoaderListener.contextInitialized(PortletContextLoaderListener.java:96)
        at com.liferay.portal.kernel.servlet.PortalClassLoaderServletContextListener.doPortalInit(PortalClassLoaderServletContextListener.java:93)
        at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
        at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:61)
        at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:53)
        at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:50)
        at com.liferay.portal.kernel.servlet.PortalClassLoaderServletContextListener.contextInitialized(PortalClassLoaderServletContextListener.java:52)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4723)
        at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226)
        at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
        at java.lang.ClassLoader.findClass(ClassLoader.java:359)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        at com.liferay.portal.spring.util.FilterClassLoader.loadClass(FilterClassLoader.java:41)
        at org.springframework.util.ClassUtils.forName(ClassUtils.java:257)
        at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(BeanDefinitionReaderUtils.java:63)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.createBeanDefinition(BeanDefinitionParserDelegate.java:616)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:472)
        ... 36 more
07:02:00,719 ERROR [PortletApplicationContext:87] org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [com.liferay.portal.da
o.shard.ShardAdvice] not found
Offending resource: ServletContext resource [/WEB-INF/classes/META-INF/shard-data-source-spring.xml]
Bean 'com.liferay.portal.dao.shard.ShardAdvice'; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.dao.shard.ShardAdvice
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [com.liferay.portal.dao.shard.ShardAdvice] not found
Offending resource: ServletContext resource [/WEB-INF/classes/META-INF/shard-data-source-spring.xml]
Bean 'com.liferay.portal.dao.shard.ShardAdvice'; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.dao.shard.ShardAdvice
        at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
        at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:291)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:491)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:396)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:365)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:258)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:153)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:132)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
        at com.liferay.portal.spring.context.PortletApplicationContext.loadBeanDefinitions(PortletApplicationContext.java:76)
        at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93)
        at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
        at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
        at com.liferay.portal.spring.context.PortletContextLoaderListener.contextInitialized(PortletContextLoaderListener.java:96)
        at com.liferay.portal.kernel.servlet.PortalClassLoaderServletContextListener.doPortalInit(PortalClassLoaderServletContextListener.java:93)
        at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
        at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:61)
        at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:53)
        at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:50)
        at com.liferay.portal.kernel.servlet.PortalClassLoaderServletContextListener.contextInitialized(PortalClassLoaderServletContextListener.java:52)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4723)
        at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226)
        at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: com.liferay.portal.dao.shard.ShardAdvice
        at java.lang.ClassLoader.findClass(ClassLoader.java:359)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        at com.liferay.portal.spring.util.FilterClassLoader.loadClass(FilterClassLoader.java:41)
        at org.springframework.util.ClassUtils.forName(ClassUtils.java:257)
        at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(BeanDefinitionReaderUtils.java:63)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.createBeanDefinition(BeanDefinitionParserDelegate.java:616)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:472)
        ... 36 more
07:02:01,927 ERROR [ContextLoader:220] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liferaySessionFactory' defined in ServletContext resource [/WEB-INF/classes/META-INF/hiberna
te-spring.xml]: Cannot resolve reference to bean 'portletClassLoader' while setting bean property 'sessionFactoryClassLoader'; nested exception is org.springframework.beans.factory
.NoSuchBeanDefinitionException: No bean named 'portletClassLoader' is defined


Any ideas?

Regards,
Nilesh
thumbnail
Nagendra Kumar Busam, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Liferay Master Beiträge: 678 Beitrittsdatum: 07.07.09 Neueste Beiträge
Hi Nilesh,

Did you run the ant build-service once again with LR 6.1?

You know dtd declarations at top will vary from 6.0 to 6.1

If you can try to add source code, will have a look

Thanks,
- Nagendra Kumar
thumbnail
Nilesh Gundecha, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Regular Member Beiträge: 205 Beitrittsdatum: 01.12.09 Neueste Beiträge
Thanks for prompt reply.

I will try out this and get back here.

Regards,
Nilesh
thumbnail
João Cartaxo, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

New Member Beiträge: 9 Beitrittsdatum: 10.10.11 Neueste Beiträge
Hello,

I'm having the same problem... I have tried the ant-service build with Liferay-6.1-RC-SDK but the issue remains.

First, when I deploy it to the server I get this:


 ERROR [BaseDeployer:322] Unable to copy portal TLD liferay-aui.tld
java.lang.NullPointerException
        at java.io.File.<init>(File.java:222)
        at com.liferay.portal.util.FileImpl.copyFile(FileImpl.java:161)
        at com.liferay.portal.kernel.util.FileUtil.copyFile(FileUtil.java:54)
        at com.liferay.portal.tools.deploy.BaseDeployer.copyPortalDependencies(BaseDeployer.java:318)
        at com.liferay.portal.tools.deploy.BaseDeployer.deployDirectory(BaseDeployer.java:524)
        at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:889)
        at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:819)
        at com.liferay.portal.deploy.auto.PortletAutoDeployer.autoDeploy(PortletAutoDeployer.java:96)
        at com.liferay.portal.deploy.auto.PortletAutoDeployListener.deploy(PortletAutoDeployListener.java:78)
        at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.processFile(AutoDeployDir.java:180)
        at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.scanDirectory(AutoDeployDir.java:222)
        at com.liferay.portal.kernel.deploy.auto.AutoDeployScanner.run(AutoDeployScanner.java:50)
  Copying 180 files to /usr/local/liferay/tomcat/webapps/mintrans-LinkManagerV2-portlet
  Copying 1 file to /usr/local/liferay/tomcat/webapps/mintrans-LinkManagerV2-portlet
  Deleting directory /usr/local/liferay/tomcat/temp/20111223150110406
 INFO  [PortletAutoDeployListener:81] Portlets for /usr/local/liferay/deploy/mintrans-LinkManagerV2-portlet.war copied successfully. Deployment will start in a few seconds.
</init>




And when the actual deploy process starts, I get this:


ERROR [PortletApplicationContext:87] org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor] not found
Offending resource: ServletContext resource [/WEB-INF/classes/META-INF/base-spring.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor] not found
Offending resource: ServletContext resource [/WEB-INF/classes/META-INF/base-spring.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
        at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
        at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:291)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:491)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:396)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:365)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:258)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:153)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:132)
        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
        at com.liferay.portal.spring.context.PortletApplicationContext.loadBeanDefinitions(PortletApplicationContext.java:76)
        at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93)
        at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
        at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:282)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:204)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
        at com.liferay.portal.spring.context.PortletContextLoaderListener.contextInitialized(PortletContextLoaderListener.java:99)
        at com.liferay.portal.kernel.servlet.PortalClassLoaderServletContextListener.doPortalInit(PortalClassLoaderServletContextListener.java:91)
        at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
        at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:61)
        at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:53)
        at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:52)
        at com.liferay.portal.kernel.servlet.PortalClassLoaderServletContextListener.contextInitialized(PortalClassLoaderServletContextListener.java:50)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4765)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5260)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:866)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:842)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
        at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1095)
        at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1617)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
        at java.lang.ClassLoader.findClass(ClassLoader.java:358)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        at com.liferay.portal.spring.util.FilterClassLoader.loadClass(FilterClassLoader.java:41)
        at org.springframework.util.ClassUtils.forName(ClassUtils.java:257)
        at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(BeanDefinitionReaderUtils.java:63)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.createBeanDefinition(BeanDefinitionParserDelegate.java:616)
        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:472)
        ... 42 more




Can someone help me please?
thumbnail
Hitoshi Ozawa, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Liferay Legend Beiträge: 7942 Beitrittsdatum: 24.03.10 Neueste Beiträge
I've tried Liferay 6.1 and it seems some API as missing and some have been modified.
That is, it's not 100% backward compatible. (sigh)
thumbnail
Nilesh Gundecha, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Regular Member Beiträge: 205 Beitrittsdatum: 01.12.09 Neueste Beiträge
Hitoshi Ozawa:
I've tried Liferay 6.1 and it seems some API as missing and some have been modified.
That is, it's not 100% backward compatible. (sigh)



Right, I found the mostly the API changes are in ImageGallery, Organization, etc.

Regards,
Nilesh.
thumbnail
Hitoshi Ozawa, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Liferay Legend Beiträge: 7942 Beitrittsdatum: 24.03.10 Neueste Beiträge
I remember Jorge? making a remark earlier this year about changing one interface, but it seems there's actually more.
I'm not sure if this is an oversight or if it's deliberately been changed. emoticon

It, also, seems 6.1.0RC changed some packaging and some functionalities which implies it's actually in alpha testing still
in terms of normal release term usage. I'm very curious on what going to be released by the end of this year if something
is actually going to be released.
thumbnail
João Cartaxo, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

New Member Beiträge: 9 Beitrittsdatum: 10.10.11 Neueste Beiträge
Has anybody else found this problem as well?

After the official release of Liferay 6.1 CE GA-1 I was hopping that this might be solved, but it isn't....
thumbnail
Mika Koivisto, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Liferay Legend Beiträge: 1519 Beitrittsdatum: 07.08.06 Neueste Beiträge
There has been many major changes so the API will not be 100% compatible. When ever you deploy a plugin that uses servicebuilder to another version you must rerun ant build-service. That should regenerate everything to match the new version. If it still complains of servicebuilder generated file try removing the old ones and rerun ant build-service. Also I think liferay-aui.tld was renamed aui.tld.
thumbnail
Hitoshi Ozawa, geändert vor 12 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Liferay Legend Beiträge: 7942 Beitrittsdatum: 24.03.10 Neueste Beiträge
Mika, it's not just some arguments to the APIs has changed or that some API names have changed, some APIs are still "missing" from Liferay 6.1 that were present in 6.0.x.

It's really not a major problem because they can easily be added back in but it really should be supported in Liferay 6.1 instead of users having to do this.
thumbnail
Karteek S, geändert vor 11 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Junior Member Beiträge: 37 Beitrittsdatum: 05.03.12 Neueste Beiträge
HI all,

How can we add API of 6.0 to 6.1
.
Please Help me in fixing these iissues.

Thanks and Regards,
Karteek
thumbnail
Jaynil A Bagdai, geändert vor 11 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Regular Member Beiträge: 119 Beitrittsdatum: 03.03.12 Neueste Beiträge
Hi Karteek,

As what ever the API you use in 6.0 will be available in 6.1 unless and until its not deprecated.
Can you please post your issue in detail that what API you are not able to access in 6.1?

Thanks,
Jaynil
thumbnail
Karteek S, geändert vor 11 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Junior Member Beiträge: 37 Beitrittsdatum: 05.03.12 Neueste Beiträge
Hi Jaynil A Bagdai,
Thanks for your reply.
I want to upgrade my project from 6.0 to 6.1, I have followed the steps from guide.
I think it has upgraded well but it is throwing bean errors and some other errors while my portlets are deploying.

For your reference, I have attached the file to this reply.
thumbnail
Jaynil A Bagdai, geändert vor 11 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Regular Member Beiträge: 119 Beitrittsdatum: 03.03.12 Neueste Beiträge
Hi Karteek,

One of the exception lines showing like below

"Caused by: com.liferay.portal.OldServiceComponentException: Build namespace LCMSContent has build number 337 which is newer than 328"


to remove that exception go to service.properties file for which you are making service.xml and modify build number as 337.

Moreover bean exception for

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'com.liferay.portlet.imagegallery.service.IGFolderService' is defined


version 6.1 do not have API with this name so you are getting exceptions for those kind of bean classes.

Can you please try to check compilation errors in your project by importing it to IDE..

Thanks,
Jaynil
thumbnail
Sergio Romero Zayas, geändert vor 10 Jahren.

RE: Is Liferay 6.1 API backward compatible with Liferay 6.0

Regular Member Beiträge: 151 Beitrittsdatum: 14.04.08 Neueste Beiträge
Mika Koivisto:
There has been many major changes so the API will not be 100% compatible. When ever you deploy a plugin that uses servicebuilder to another version you must rerun ant build-service. That should regenerate everything to match the new version. If it still complains of servicebuilder generated file try removing the old ones and rerun ant build-service. Also I think liferay-aui.tld was renamed aui.tld.


What we do with package classes com.liferay.portlet.image gallery. *?

DuplicateImageNameException
ImageNameException
ImageSizeException
etc.

When we portlets in 6.0.x, and we need up to version 6.1.x

What we do?

Is there any part of the web where developments are cited so that the developer can migrate your portlets to the new version?

Sorry for my English. thanks in advance.

emoticon