Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

AEM 6.3.2 ThumbnailProcess.java dependency classes not available in uber-jar

suneelkandali
Level 2
Level 2

Hi,

I did extract AEM 6.3.2 uber-jar-api and took code of com.day.cq.dam.core.process.ThumbnailProcess and put in my local project and tried build with 6.3.2 jar, but below highiighted classes threw error that "not found".  These classes are not available in uber-jar, do you know in which jar these classes are available?

import com.day.cq.dam.api.Asset;

import com.day.cq.dam.api.renditions.RenditionMaker;

import com.day.cq.dam.commons.process.AbstractAssetWorkflowProcess;

import com.day.cq.dam.commons.util.AssetUpdate;

import com.day.cq.dam.commons.util.AssetUpdate.Check;

import com.day.cq.dam.commons.util.AssetUpdateMonitor;

import com.day.cq.dam.commons.util.DamUtil;

import com.day.cq.dam.core.impl.process.CreateFPORenditionProcess;

import com.day.cq.dam.core.impl.process.CreateFPORenditionProcess.Config;

import com.day.cq.dam.core.impl.ui.preview.FolderPreviewUpdater;

import com.day.cq.workflow.WorkflowException;

import com.day.cq.workflow.WorkflowSession;

import com.day.cq.workflow.exec.WorkItem;

import com.day.cq.workflow.exec.WorkflowData;

import com.day.cq.workflow.metadata.MetaDataMap;

import javax.jcr.Node;

import javax.jcr.RepositoryException;

import org.apache.commons.lang.StringUtils;

import org.apache.felix.scr.annotations.Component;

import org.apache.felix.scr.annotations.Reference;

import org.apache.felix.scr.annotations.Service;

import org.slf4j.Logger;

import org.slf4j.LoggerFactory;

Thanks for your help,

Suneel

2 Replies
Arun_Patidar
Community Advisor
Community Advisor

Hi,

These classes are part of below bundle

Day Communique 5 DAM Core Implementation (com.day.cq.dam.cq-dam-core)

Jörg_Hoh
Employee
Employee

These classes are not exported by any bundle, because they are implementation classes. They are neither designed to inherit from nor from being called from any other services (except through their service interface).

So importing them does not work.

Jörg