-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
message bundle registration #116
Comments
Where does it use search exactly? |
RepositoryLocation repositoryLocation = new RepositoryLocation(rootNodeRef.getStoreRef(), path, RepositoryLocation.LANGUAGE_PATH); This is it, I guess. |
The eager initialisation causes the problem: if it is called before the property files are indexed, the files are never loaded:
(only an issue the very first time you deploy a file, like in a production deployment) |
That probably explains why we it only sometimes worked. To me it is an Alfresco issue, because with bad timing, you also have this without DE. Restarting should help in this case. (but that is against the DE philosophy) |
Deploying twice also fixes the issue, but ... I remember the eager loading was also a workaround for another Alfresco bug. (no transaction in scope) To verify if that workaround is still required from Alfresco >= 5. |
The message bundle registration added in 1.3 is very unreliable when using solr.
The MessagServiceImpl uses search to locate the properties files, meaning the files cannot be found at the time of registration unless they already existed.
The text was updated successfully, but these errors were encountered: