1. Home
  2. Development
  3. Service Builder Liferay-Require-SchemaVersion update

Service Builder Liferay-Require-SchemaVersion update

Bernd S, modified 5 Years ago.
Service Builder Liferay-Require-SchemaVersion update
Junior Member Posts: 59 Join Date: 3/31/15 Recent Posts
Hello,

I am working on a service builder project using Liferay 7.0 and Maven. Up until now I was developing version 0.1.x, which is set in my parent pom and in service builder's bnd.bnd. Today I updated this version to 0.2.0 since I made some bigger changes.

Unfortunately as soon as I make this change the service builder is no longer visible inside Liferay. I even get a successful startup message with the new version but the services don't show up. As soon as I revert to 0.1.x it shows up again.

I already cleaned all tmp/work directories, deployed multiple times and restarted the whole server. No success.

Only clues I found so far are:
  • one entry for my portlet with version 0.1.0 in RELEASE_ table of Liferay
  • articles about complex Liferay upgrade proccesses
Since I am using an external database for my service builder project I'd like keep it as simple as possible and refrain from using such an upgrade process. Is there an easier way to get my project working again?

Best regards,
Bernd
Bernd S, modified 5 Years ago.
RE: Service Builder Liferay-Require-SchemaVersion update
Junior Member Posts: 59 Join Date: 3/31/15 Recent Posts
Got it to work by deleting all entries related to my service in Liferay's RELEASE_ and SERVICECOMPONENT tables.
I am aware that I loose some Liferay features (rollback to previous version) but I prefere to handle those tasks externally anyways.

Did I miss anything critical?
thumbnail
David H Nebinger, modified 5 Years ago.
RE: Service Builder Liferay-Require-SchemaVersion update
Liferay Legend Posts: 14933 Join Date: 9/2/06 Recent Posts
By "significant changes" are you talking about table structure changes?

If so, are you including portal-developer.properties?

If yes to first and no to second, SB schema changes are not automatically deployed, so in order for your service to be up to 0.2.0 you need to write an upgrade step to get from "0.1.0" to "0.2.0" to apply the DDL changes.  Enabling portal-developer.properties pulls in the setting to allow SB to apply schema changes, but this is not meant to be used in production.