Just curious whether Alfresco supposed to upgrade repository automatically after SVN-update/build or it is required to start with clear repository each time? I’ve just upgraded the server from revision 109 (14/12/2006 just after WCM was merged into HEAD) to 399 (25/01/2007) and receive an error when access existing web projects:
[size=75]Caused by: org.alfresco.service.cmr.avm.AVMNotFoundException: Store not found. at org.alfresco.repo.avm.AVMRepository.getListing(AVMRepository.java:887) at org.alfresco.repo.avm.AVMServiceImpl.getDirectoryListing(AVMServiceImpl.java:198) at org.alfresco.repo.avm.AVMServiceImpl.getDirectoryListing(AVMServiceImpl.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:335) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java: 181) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148) at org.alfresco.repo.transaction.RetryingTransactionAdvice.invoke(RetryingTransactionAdvice.java:92) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176) at $Proxy57.getDirectoryListing(Unknown Source) at org.alfresco.web.bean.wcm.AVMBrowseBean.getWebapps(AVMBrowseBean.java:414) at org.alfresco.web.bean.wcm.AVMBrowseBean.getWebappsSize(AVMBrowseBean.java:430)[/size]
While everything is OK when I create new web projects from scratch. Any suggestions how to manually upgrade the repository?
PS: I know that WCM functionality is just in community preview stage PSS: tried to Export/Import full repository - same result…
If you are taking cuts of the code from SVN at any time then you are not guaranteed to get a working system at all I would suggest you create a fresh DB instance each time if you are doing this. We can only ensure an upgrade path between specific releases. And I know for a fact that a fresh database instance will be required several times over between the two dates you mention
That’s actually understandable as probably it would be too much overhead for the project to update the repository for each SVN commit. Just had hopes for a miracle. Any way we’ve already moved all our data manually as we at the moment have only couple of “prove of concept†projects deployed.