LR 6.1.0 Service Builder

[mohammad azaruddin, geändert vor 11 Jahren.]

Hi All
In my service.xml i have modified one column and removed one column..After build service and deploy, the database table is uneffected..Long before i had faced same issue and i resolved it but i dont know how..Is there any valid solution for this

Regards
azhar

[Subhash Pavuskar, geändert vor 11 Jahren.]

Hi,

Remove jar from WEB-INF->Lib folder and then rebuild your service !!

[mohammad azaruddin, geändert vor 11 Jahren.]

Hi
It is not working..i deleted the serive.jar and rebuild service..new service.jar is created but no use.

Regards
azhar

[Subhash Pavuskar, geändert vor 11 Jahren.]

your tomcat is in running condition right ?

[mohammad azaruddin, geändert vor 11 Jahren.]

Hi

Yes.server is currently running

[Subhash Pavuskar, geändert vor 11 Jahren.]

can you share your service.xml code and if error message from console !!!

[mohammad azaruddin, geändert vor 11 Jahren.]

Old servic.xml or new...?
i changed the name of primary key column and i deleted another column...

<entity name="Project" local-service="true" remote-service="false">
<column name="RecId" type="long" primary="true" />
<column name="ProjectId" type="long" />
<column name="ProjectName" type="String" />

changed to

<entity name="Project" local-service="true" remote-service="false">
<column name="ProjectId" type="long" primary="true" />
<column name="ProjectName" type="String" />

And no error in console..

[Subhash Pavuskar, geändert vor 11 Jahren.]

try this one !! 1st check serviceComponent table from your databse !! The build.number in service.properties must be higher than that, stored in servicecomponent if its like that then change it to the value higher value in your service.properties !! then rebuild your service !!

[mohammad azaruddin, geändert vor 11 Jahren.]

Hi Subhash Pavuskar

Subhash Pavuskar:

try this one !! 1st check serviceComponent table from your databse !! The build.number in service.properties must be higher than that, stored in servicecomponent if its like that then change it to the value higher value in your service.properties !! then rebuild your service !!

there was one warning while building service layer even though it was showing build successful.
I learnt two things today 1)we are not supposed to ignore the warning while building service
2) build.number issue
And it is working fine now
Regards
Azhar

[Subhash Pavuskar, geändert vor 11 Jahren.]

Yeah i know bcs even i too faced same problem long back !!

[Jitendra Rajput, geändert vor 11 Jahren.]

You can also verify from the logs if your service changes are applied or not .

Upgrading " + buildNamespace +" database to build number " + buildNumber
Upgrading database with tables.sql......

[mohammad azaruddin, geändert vor 11 Jahren.]

Jitendra Rajput:

You can also verify from the logs if your service changes are applied or not .

Upgrading " + buildNamespace +" database to build number " + buildNumber
Upgrading database with tables.sql......

how to check using above code....?litle confused

[Jitendra Rajput, geändert vor 11 Jahren.]

This is not the code i just gave you example log..
Logs will be like this

Upgrading test_Portlet database to build number 100
Upgrading database with tables.sql......

[mohammad azaruddin, geändert vor 11 Jahren.]

Okay..Now almost clear about it.....it ll throw below mentioned exception if there is some problem with service..am i right...?

Build namespace UNIVERSITY has build number 15 which is newer than 10

[Jitendra Rajput, geändert vor 11 Jahren.]

Check my post on build number space error.

http://itsliferay.blogspot.in/2012/04/build-number-deployment-error.html

[mohammad azaruddin, geändert vor 11 Jahren.]

Jitendra Rajput:

Check my post on build number space error.

http://itsliferay.blogspot.in/2012/04/build-number-deployment-error.html

This blog is familiar to me.Thank you for sharing your knowledge

Regards
azhar

[mohammad azaruddin, geändert vor 11 Jahren.]

Also tables.sql file is uneffected.Should i delete the .java classes genereted by the service layer..?Or this problem is specific to LR 6.1.0..?