ServiceBuilder is Importing petra StringBundler instead of kernel.StringBun

RE: ServiceBuilder is Importing petra StringBundler instead of kernel.Strin

2019-08-26T09:10:21Z

After updated dependency as below issue is resolved.Before : compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "3.64.1" After (working) : compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "3.0.0"

RE: ServiceBuilder is Importing petra StringBundler instead of kernel.Strin

2018-10-26T20:33:20Z

David Ilechukwu

How do I resolve this please? Is this a servicebuilder issue?

Yes, it's a service builder issue. I'm not exactly sure why this thread was forked from your other thread, but you can read the reply there for ways to resolve the issue.

RE: ServiceBuilder is Importing petra StringBundler instead of kernel.Strin

2018-10-24T08:10:19Z

Michel Schmidt
However, the blogs-service module source code shows that the service builder uses the 7.1.0 servicebuilder and yet the generated -ServiceImplPersistence classes import the com.liferay.portal.kernel.util.StringBundler class rather than com.liferay.petra.string.StringBundler - wondering how that works.

From what I can see, the dependency changed in most modules from com.liferay.portal.kernel.util.StringBundler to com.liferay.petra.string.StringBundler (both in the 7.1-branch and also in the master-branch).

Some examples: Here, here, here, here and here.

I also have ported a customized liferay core app to 7.1 and remember having done the same.

Many thanks Michel - for your quick reply! Yes, you're right. There's been a change in dependency from kernel StringBundler to petra package StringBundler (I've even included those same petra package dependencies in my own build.gradle). See here...

buildscript {
&nbsp; &nbsp; dependencies {
&nbsp; &nbsp; &nbsp; &nbsp; classpath group: "com.liferay", name: "com.liferay.gradle.plugins.service.builder", version: "2.1.61"
&nbsp; &nbsp; }
&nbsp; &nbsp; repositories {
&nbsp; &nbsp; &nbsp; &nbsp; maven {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; url "https://repository-cdn.liferay.com/nexus/content/groups/public"
&nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; }
} &nbsp; &nbsp;
apply plugin: "com.liferay.portal.tools.service.builder"
dependencies {
&nbsp; &nbsp; compileOnly group: "biz.aQute.bnd", name: "biz.aQute.bndlib", version: "3.1.0"
&nbsp; &nbsp; compileOnly group: "com.liferay", name: "com.liferay.portal.spring.extender.api", version: "3.0.0"
&nbsp; &nbsp; compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "3.0.0"
&nbsp; &nbsp; compileOnly group: "com.liferay", name: "com.liferay.petra.function", version: "2.0.0"
&nbsp; &nbsp; compileOnly group: "com.liferay", name: "com.liferay.petra.model.adapter", version: "2.0.0"
&nbsp; &nbsp; compileOnly group: "com.liferay", name: "com.liferay.petra.reflect", version: "2.0.0"
&nbsp; &nbsp; compileOnly group: "com.liferay", name: "com.liferay.petra.string", version: "2.0.0" &nbsp; &nbsp;
&nbsp; &nbsp; compileOnly group: "com.liferay", name: "com.liferay.portal.dao.orm.custom.sql.api", version: "1.0.0"
&nbsp; &nbsp; compileOnly group: "javax.portlet", name: "portlet-api", version: "3.0.0"
&nbsp; &nbsp; compileOnly group: "javax.servlet", name: "javax.servlet-api", version: "3.0.1"
&nbsp; &nbsp; compileOnly group: "org.osgi", name: "org.osgi.core", version: "5.0.0"
&nbsp; &nbsp; compileOnly group: "org.osgi", name: "org.osgi.service.component.annotations", version: "1.3.0" &nbsp; &nbsp;
&nbsp; &nbsp; compileOnly project(":hrm_core-api")
}

But why then does the code generated by ServiceBuilder in my -ServicePersistenceImpl classes throw compile errors like this...

C:\Software\Devel\Src\Web\Component\hrm_core\hrm_core-service\src\main\java\com\tpl\pmedics\hrm_core\service\persistence\impl\JobVacancyPersistenceImpl.java:734: error: incompatible types: com.liferay.petra.string.StringBundler cannot be converted to com.liferay.portal.kernel.util.StringBundler
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; appendOrderByComparator(query, _ORDER_BY_ENTITY_ALIAS,

Apparently, the generated code is expecting the "query" object to be an instance of com.liferay.portal.kernel.util.StringBundler rather than com.liferay.petra.string.StringBundler in this method...

&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;if (orderByComparator != null) {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;appendOrderByComparator(query, _ORDER_BY_ENTITY_ALIAS,
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;orderByComparator);
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;}

How do I resolve this please? Is this a servicebuilder issue?

Thanks.

RE: ServiceBuilder is Importing petra StringBundler instead of kernel.Strin

2018-10-24T05:58:00Z

However, the blogs-service module source code shows that the service builder uses the 7.1.0 servicebuilder and yet the generated -ServiceImplPersistence classes import the com.liferay.portal.kernel.util.StringBundler class rather than com.liferay.petra.string.StringBundler - wondering how that works.

From what I can see, the dependency changed in most modules from com.liferay.portal.kernel.util.StringBundler to com.liferay.petra.string.StringBundler (both in the 7.1-branch and also in the master-branch).

Some examples: Here, here, here, here and here.

I also have ported a customized liferay core app to 7.1 and remember having done the same.

ServiceBuilder is Importing petra StringBundler instead of kernel.StringBun

2018-10-24T02:40:26Z

Hello folks!
The -ServicePersistenceImpl classes generated by ServiceBuilder all import the com.liferay.petra.string.StringBundler class instead of the com.liferay.portal.kernel.util.StringBundler class. This causes an compile error in the

appendOrderByComparator(query, _ORDER_BY_ENTITY_ALIAS,
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;orderByComparator)

method which is expecting a query argument of type com.liferay.portal.kernel.util.StringBundler.

The following error is thrown

C:\Software\Devel\Src\Web\Component\hrm_core\hrm_core-service\src\main\java\com\tpl\pmedics\hrm_core\service\persistence\impl\JobVacancyPersistenceImpl.java:231: error: incompatible types: com.liferay.petra.string.StringBundler cannot be converted to com.liferay.portal.kernel.util.StringBundler
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; appendOrderByComparator(query, _ORDER_BY_ENTITY_ALIAS,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ^
C:\Software\Devel\Src\Web\Component\hrm_core\hrm_core-service\src\main\java\com\tpl\pmedics\hrm_core\service\persistence\impl\JobVacancyPersistenceImpl.java:734: error: incompatible types: com.liferay.petra.string.StringBundler cannot be converted to com.liferay.portal.kernel.util.StringBundler
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; appendOrderByComparator(query, _ORDER_BY_ENTITY_ALIAS,

I'm using ServiceBuilder plugin declared as follows in my build.gradle

buildscript {
&nbsp; &nbsp; dependencies {
&nbsp; &nbsp; &nbsp; &nbsp; classpath group: "com.liferay", name: "com.liferay.gradle.plugins.service.builder", version: "2.1.61"
&nbsp; &nbsp; }
&nbsp; &nbsp; repositories {
&nbsp; &nbsp; &nbsp; &nbsp; maven {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; url "https://repository-cdn.liferay.com/nexus/content/groups/public"
&nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; }
} &nbsp; &nbsp;
apply plugin: "com.liferay.portal.tools.service.builder"

Also, I noticed that servicebuilder started importing the petra package StringBundler after I changed the dtd declaration in my service.xml file from

It imports the com.liferay.portal.kernel.util.StringBundler class when the dtd is 7.0.0 rather than 7.1.0

However, the blogs-service module source code shows that the service builder uses the 7.1.0 servicebuilder and yet the generated -ServiceImplPersistence classes import the com.liferay.portal.kernel.util.StringBundler class rather than com.liferay.petra.string.StringBundler - wondering how that works.

Any helps, please? Searched around without any mention of this kind of occurence.