Service-builder mod stop working when adding @ServiceReference to CustomSQL

RE: Service-builder mod stop working when adding @ServiceReference to Custo

2018-11-14T00:20:54Z

Hi David,

I used ServiceReference since it's mentioned on this tutorial.

Just tried @Reference (all 3 of them) and none worked (2 were disallowed on that location).

Unless you tell me that using CustomSQLUtil has a very bad side effect, I'll stick to it, since it's working. :-)

Thanks

Fernando

RE: Service-builder mod stop working when adding @ServiceReference to Custo

2018-11-13T23:22:22Z

Well, CustomSQLUtil will be using a ServiceTracker to get the instance to the CustomSQL class. So maybe it is not a @ServiceReference you need, and just a regular @Reference...

RE: Service-builder mod stop working when adding @ServiceReference to Custo

2018-11-13T22:43:46Z

Hi David,

In this situation, the scr:list 555 comes up empty. Also, the ds:unsatisfied command only lists the portlet as missing one dependency: the service itself.

I found out that I just need to comment the @ServiceReference(type=CustomSQL.class) line and use CustomSQLUtil instead of the @referenced variable so that it starts working.

I'd really like to understand what's happening but now that it's working I think I'll move forward.

Thanks

Fernando

RE: Service-builder mod stop working when adding @ServiceReference to Custo

2018-11-12T12:38:56Z

So from your lb output command above, normally I get the list of components like:

scr:list 555

That gives the list of components in a bundle and should show general state for them. Each one will be listed with a component id, so I use that with the scr:info command argument to get the details on each component.

I've never been successful w/ the search by name option; I'm sure there's a trick for it, but since I have a working path I haven't looked into it further.

RE: Service-builder mod stop working when adding @ServiceReference to Custo

2018-11-12T11:02:26Z

Hi David,

Sorry, I'm not sure I'm following... I tried three ways:

g! scr:info com.test.example13.sb.service.CustomerService No Component with name or configuration with ID matching com.test.example13.sb.service.CustomerService g! scr:info com.test.example13.sb.service                 No Component with name or configuration with ID matching com.test.example13.sb.service g! scr:info Example13service-service No Component with name or configuration with ID matching Example13service-service

Still, I have both modules of the service as STARTED...

... and the *-service module is declaring:

g! headers 555

Example13service-service (555) ------------------------------ Manifest-Version = 1.0 Bnd-LastModified = 1541758479786 Bundle-ManifestVersion = 2 Bundle-Name = Example13service-service Bundle-SymbolicName = com.test.example13.sb.service Bundle-Version = 1.0.0 Created-By = 1.8.0_191 (Oracle Corporation) Export-Package = com.test.example13.sb.exception;version="1.0.0";uses:="com.liferay.portal.kernel.exception",com.test.example13.sb.model;version="1.0.0";uses:="com.liferay.expando.kernel.model,com.liferay.exportimport.kernel.lar,com.liferay.portal.kernel.annotation,com.liferay.portal.kernel.bean,com.liferay.portal.kernel.model,com.liferay.portal.kernel.service,com.liferay.portal.kernel.util",com.test.example13.sb.model.impl;uses:="com.liferay.expando.kernel.model,com.liferay.exportimport.kernel.lar,com.liferay.portal.kernel.json,com.liferay.portal.kernel.model,com.liferay.portal.kernel.model.impl,com.liferay.portal.kernel.service,com.test.example13.sb.model";version="1.0.0",com.test.example13.sb.service;version="1.0.0";uses:="com.liferay.exportimport.kernel.lar,com.liferay.portal.kernel.dao.orm,com.liferay.portal.kernel.exception,com.liferay.portal.kernel.jsonwebservice,com.liferay.portal.kernel.model,com.liferay.portal.kernel.search,com.liferay.portal.kernel.security.access.control,com.liferay.portal.kernel.service,com.liferay.portal.kernel.spring.osgi,com.liferay.portal.kernel.transaction,com.liferay.portal.kernel.util,com.test.example13.sb.model",com.test.example13.sb.service.base;uses:="com.liferay.counter.kernel.service,com.liferay.exportimport.kernel.lar,com.liferay.portal.kernel.bean,com.liferay.portal.kernel.dao.orm,com.liferay.portal.kernel.exception,com.liferay.portal.kernel.model,com.liferay.portal.kernel.module.framework.service,com.liferay.portal.kernel.search,com.liferay.portal.kernel.service,com.liferay.portal.kernel.service.persistence,com.liferay.portal.kernel.transaction,com.liferay.portal.kernel.util,com.liferay.portal.spring.extender.service,com.test.example13.sb.model,com.test.example13.sb.service,com.test.example13.sb.service.persistence";version="1.0.0",com.test.example13.sb.service.http;uses:="com.liferay.portal.kernel.exception,com.liferay.portal.kernel.security.auth,com.test.example13.sb.model";version="1.0.0",com.test.example13.sb.service.impl;uses:="com.liferay.portal.kernel.exception,com.test.example13.sb.model,com.test.example13.sb.service.base";version="1.0.0",com.test.example13.sb.service.persistence;version="1.0.0";uses:="com.liferay.portal.kernel.dao.orm,com.liferay.portal.kernel.service,com.liferay.portal.kernel.service.persistence,com.liferay.portal.kernel.util,com.test.example13.sb.exception,com.test.example13.sb.model",com.test.example13.sb.service.persistence.impl;uses:="com.liferay.portal.kernel.bean,com.liferay.portal.kernel.dao.orm,com.liferay.portal.kernel.exception,com.liferay.portal.kernel.model,com.liferay.portal.kernel.service.persistence,com.liferay.portal.kernel.service.persistence.impl,com.liferay.portal.kernel.util,com.liferay.portal.spring.extender.service,com.test.example13.sb.exception,com.test.example13.sb.model,com.test.example13.sb.model.impl,com.test.example13.sb.service.persistence";version="1.0.0",com.test.example13.sb.service.util;uses:="com.liferay.portal.kernel.configuration";version="1.0.0" Import-Package = com.liferay.counter.kernel.service;version="[1.0,2)",com.liferay.expando.kernel.model;version="[1.0,2)",com.liferay.expando.kernel.util;version="[1.0,2)",com.liferay.exportimport.kernel.lar;version="[1.1,2)",com.liferay.portal.dao.orm.custom.sql;version="[1.0,2)",com.liferay.portal.kernel.annotation;version="[6.3,7)",com.liferay.portal.kernel.bean;version="[7.0,8)",com.liferay.portal.kernel.configuration;version="[6.2,7)",com.liferay.portal.kernel.dao.db;version="[7.1,8)",com.liferay.portal.kernel.dao.jdbc;version="[7.1,8)",com.liferay.portal.kernel.dao.orm;version="[7.0,8)",com.liferay.portal.kernel.exception;version="[7.0,8)",com.liferay.portal.kernel.json;version="[7.0,8)",com.liferay.portal.kernel.jsonwebservice;version="[7.0,8)",com.liferay.portal.kernel.log;version="[7.0,8)",com.liferay.portal.kernel.model;version="[1.0,1.1)",com.liferay.portal.kernel.model.impl;version="[1.0,2)",com.liferay.portal.kernel.module.framework.service;version="[1.0,2)",com.liferay.portal.kernel.search;version="[7.2,8)",com.liferay.portal.kernel.security.access.control;version="[1.0,2)",com.liferay.portal.kernel.security.auth;version="[1.0,2)",com.liferay.portal.kernel.service;version="[1.3,2)",com.liferay.portal.kernel.service.http;version="[1.0,2)",com.liferay.portal.kernel.service.persistence;version="[1.1,2)",com.liferay.portal.kernel.service.persistence.impl;version="[1.2,2)",com.liferay.portal.kernel.spring.osgi;version="[1.0,2)",com.liferay.portal.kernel.transaction;version="[7.0,8)",com.liferay.portal.kernel.util;version="[7.3,8)",com.liferay.portal.kernel.uuid;version="[6.2,7)",com.liferay.portal.spring.extender.service;version="[1.0,2)",com.test.example13.sb.exception;version="[1.0,2)",com.test.example13.sb.model;version="[1.0,1.1)",com.test.example13.sb.model.impl,com.test.example13.sb.service;version="[1.0,1.1)",com.test.example13.sb.service.base,com.test.example13.sb.service.persistence;version="[1.0,1.1)",com.test.example13.sb.service.util,javax.sql,org.osgi.framework,org.osgi.util.tracker Javac-Debug = on Javac-Deprecation = off Javac-Encoding = Cp1252 Liferay-Require-SchemaVersion = 1.0.0 Liferay-Service = true Liferay-Spring-Context = META-INF/spring Provide-Capability = osgi.service;objectClass:List<String>="com.test.example13.sb.service.CustomerLocalService",osgi.service;objectClass:List<String>="com.test.example13.sb.service.CustomerService" Require-Capability = liferay.extender;filter:="(&(liferay.extender=spring.extender)(version>=2.0)(!(version>=3.0)))",osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))" Tool = Bnd-3.5.0.201709291849

Any ideas?

TIA

Fernando

RE: Service-builder mod stop working when adding @ServiceReference to Custo

2018-11-11T14:40:53Z

If that service is claiming an unsatisfied reference on CustomerService, then you have to check the scr:info on that instance...

Service-builder mod stop working when adding @ServiceReference to CustomSQL

2018-11-09T10:23:56Z

Hi all,

I'm trying to add custom SQL to a service-builder module managing a sample customer entity. The service is working well without custom-sql and I'm following this tutorial plus some other sources. The problem is that, as soon as I add this lines of code to CustomerFinderImpl.java...

@ServiceReference(type=CustomSQL.class) private CustomSQL _customSQL;

... the service stops working (meaning it's no longer available to a portlet using it and is no longer available on the JSONWS API page).

It's strange because both modules (-api and -service) are shown as starting on the server log (I have to force "refresh of the -api bundle on gogo shell) and are also listed as Active on the gogo shell console.

Even the portlet using the service starts, but if I do a scr:info on it's class it will show an unsatisfied reference:

*** Bundle: com.test.example13 (559) Component Description:   Name: com.test.example13.portlet.Example13Portlet   Implementation Class: com.test.example13.portlet.Example13Portlet   Default State: enabled   Activation: immediate   Configuration Policy: optional   Activate Method: insertDummyData   Deactivate Method: deactivate   Modified Method: -   Configuration Pid: [com.test.example13.portlet.Example13Portlet]   Services:      javax.portlet.Portlet   Service Scope: singleton   Reference: customerService     Interface Name: com.test.example13.sb.service.CustomerService     Cardinality: 1..1     Policy: static     Policy option: reluctant     Reference Scope: bundle   Component Description Properties:       com.liferay.portlet.display-category = category.sample       com.liferay.portlet.instanceable = true       javax.portlet.init-param.template-path = /       javax.portlet.init-param.view-template = /view.jsp       javax.portlet.name = example13       javax.portlet.resource-bundle = content.Language       javax.portlet.security-role-ref = power-user,user   Component Configuration:     ComponentId: 2571     State: unsatisfied reference     UnsatisfiedReference: customerService       Target: null       (no target services)     Component Configuration Properties:         com.liferay.portlet.display-category = category.sample         com.liferay.portlet.instanceable = true         component.id = 2571         component.name = com.test.example13.portlet.Example13Portlet         javax.portlet.init-param.template-path = /         javax.portlet.init-param.view-template = /view.jsp         javax.portlet.name = example13         javax.portlet.resource-bundle = content.Language         javax.portlet.security-role-ref = power-user,user

Previuosly it didn't compile, but adding "compile "com.liferay:com.liferay.portal.dao.orm.custom.sql:1.0.3" to build.gradle solved the building problem.

I'm doing this with Liferay 7.0 CE GA7 and IDE 3.4 (with blade and Liferay Workspace up-to-date).

Any ideas?

TIA

Fernando