DynamicQuery and Liferay 7.1 OSGI service modules

RE: DynamicQuery and Liferay 7.1 OSGI service modules

2019-03-20T13:12:59Z

You're preaching to the choir, brother.

RE: DynamicQuery and Liferay 7.1 OSGI service modules

2019-03-20T11:48:56Z

Thanks! Great information, would be nice if this kind of information was in the documentation. Would be nice to see something like that in the JavaDoc.

RE: DynamicQuery and Liferay 7.1 OSGI service modules

2019-03-19T20:23:08Z

Try using the following:

DynamicQuery dynamicQuery = myClassLocalService.dynamicQuery();

The static utils should not be used and honestly the "this.getClassLoader()" thing is too dependent upon the context it is invoked in to ensure the right class loader gets used.

The dynamicQuery() method, available on all Service Builder local services, returns a DQ object ready to deal with the queries against the model interface defined for the local service. It takes all of the guesswork out of the construction and eliminates the class loader context issues faced by code in different modules.

DynamicQuery and Liferay 7.1 OSGI service modules

2019-03-19T14:26:44Z

With the new implementation of OSGI modules in the service layer for Liferay 7.1, is there a way to use the DynamicQuery API without creating a FinderImpl? In 6.2 I could just call the DynamicQuery API from the XxxLocalServiceImpl.java code

DynamicQuery dynamicQuery = DynamicQueryFactoryUtil.forClass(MyClass.class, this.getClassLoader());

dynamicQuery.add(junction).addOrder(OrderFactoryUtil.desc("createDate"));

List<myclass> rosterReviews = this.dynamicQuery(dynamicQuery);</myclass>

In 7.1 the above code simply returns an empty List. Whereas a call to XxxLocalServiceUtil.findByxXX() returns the actual data. I would prefer not having to create a whole other class for DynamicQuery calls..