True, the IndexableActionableDynamicQuery method in a [Your Entitiy]LocalServiceBaseImpl is only created if the type of the primary key in that entity is "long".
Also, if you look at the code of that method:
@Override
public IndexableActionableDynamicQuery
getIndexableActionableDynamicQuery() {
IndexableActionableDynamicQuery indexableActionableDynamicQuery =
new IndexableActionableDynamicQuery();
indexableActionableDynamicQuery.setBaseLocalService(
deviceBindingLocalService);
indexableActionableDynamicQuery.setClassLoader(getClassLoader());
indexableActionableDynamicQuery.setModelClass(DeviceBinding.class);
indexableActionableDynamicQuery.setPrimaryKeyPropertyName("autoId");
return indexableActionableDynamicQuery;
}
there can only be one property set as the primary key. So that excludes tables with composite primary keys from indexing.
I've also noticed that Liferay Service Builer requires one primary key to be present in every entity.
Together with the necessary fields for workflow status, site management and audits that gives a clear picture of how to design a DB, if you want to integrate it with the powerful Liferay features. :-)
