How to prevent this from appearing in the logs: com.liferay.portal.kernel.exception.OldServiceComponentException: Build namespace Test has build number 23 which is newer than 3 in server level using XML file.
Kind Regards, Kiran.
How to prevent this from appearing in the logs: com.liferay.portal.kernel.exception.OldServiceComponentException: Build namespace Test has build number 23 which is newer than 3 in server level using XML file.
Kind Regards, Kiran.
On
@quatax explanation is correct but I would argue with the solution and prevention.
Prevention:
Solution:
The fix would be as mentioned above to increase the number in the file to satisfy the check.
Alternatively, you can adjust your DB entry that holds the version information. THIS IS ONLY FOR LOCAL DEV DATABASES SCENARIO.
Explanation
This is a Service Builder issue.
Each Service Builder module has a
service.xmlin which a<namespace></namespace>is defined, in your caseTest. Every module sharing this namespace has to be deployed with the same build number, which is defined insrc/main/resources/service.propertiesand will be increased by one each time you rebuild your module with the Service Builder.Resolution
Go through your Service Builder modules and check if all service.properties files of each namespace have the same
build.number.Guessing from the log you provided, one module has the build number 23 and the one you're trying to deploy has the build number 3, so setting all build numbers of the
Testnamespace to 23 should fix the problem.Prevention
To prevent this from happening again, make sure that you only run the service builder from the top directory of your project and not from within a module's directory.
This way the Service Builder will rebuild all of your Service Builder modules and therefore increase all of their build numbers by one, so they stay the same.