topic Re: problem boostraping model after OS migration in Alfresco Archive

problem boostraping model after OS migration

zomurn — Tue, 23 Feb 2010 11:54:42 GMT

Hello,Taking the same alfresco.war, alf_data+db from windows to linux, causes a boostrap problem : not any changes in the application code.I really don't understand this error causes (certainly) by a side effect.Because this URI is well imported in msc_model.xml and and well defined in another modul

Re: problem boostraping model after OS migration

ssaravanan — Tue, 23 Feb 2010 12:32:01 GMT

It means some jar bundle is missing in the tomcat/webapps/alfresco/WEB_INF/lib folder
You have copied the alfresco.war , alf_data, db, thats correct, in theory it should work
with the migration from windows to linux. But you have done some custom implementation
which I could read from the logs, the vendor probably had compiled his code as jar file
and copied it over to the tomcat/webapps/alfresco/WEB_INF/lib folder once alfresco folder
is expanded in tomcat/webapps , so ideally if you copy the missing jar file or copy
the exploded tomcat/webapps/alfresco folder as well, then that will fix the issue

Re: problem boostraping model after OS migration

zomurn — Thu, 04 Mar 2010 09:16:10 GMT

I have a look a bit closer to this problem and it still exists.
I checked for librairies into WEB-INF/lib as you said and all seems correct.
I do exactly the same archive build and deployment that in windows….the "bundle" is the same.
There is probably a sadly side effect somewhere else ! I fear that's not easy to find the problem. :cry:

Re: problem boostraping model after OS migration

piousbox — Wed, 08 Sep 2010 19:53:20 GMT

My guess is that somewhere, the same namespace is associated with a different uri, or this uri is associated with some different namespace

Caused by: org.alfresco.service.namespace.NamespaceException: URI http://www.opsera.com/opsera/model/0.1 cannot be imported as it is not defined (with prefix opsera‍

To iterate, I think http://www.opsera.com/opsera/model/0.1 does not correlate with opsera. It could be as simple as that you should use uri http://www.opsera.com/opsera/0.1 but then, I don't know for sure.