That's a valid point @Ganthimathi_R , and TBH I'm not sure what other alternative Adobe might have for on-prem scenarios.
However, considering that AEMaaCS is the future where Adobe is moving towards, I doubt if any investment is done on features for on-prem scenarios as these cases will go lesser...
I think for what you're after, you need query builder instead of Assets API.
Try this: http://localhost:4502/bin/querybuilder.json?path=/content/dam&1_property=jcr:primaryType&1_property.value=sling:Folder
You should get a JSON output with a list of all folders inside DAM:
Folder structure in...
With Adobe moving towards AEM as a cloud service, there isn't a need for setting up asset offloading anymore, since this is now handled by the asset micro-services. That's why Adobe would have deprecated the feature.
Overview on asset micrservices for asset ingestion: https://experienceleague.adob...
You need to submit to an HTTPS end point.
On your local, enable HTTPS using self signed certificates. You can download the certificates from here and also watch the video on how to enable HTTPS on your local: https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/security/use-...
I have the below folder structure in my AEM Assets containing a parent folder ('my-assets') which again contains 3 assets and 1 folder:
The Assets API on 'my-assets' folder returns below:
It is clear I see that for assets the 'properties' element has 'metadata' and dc:format' elements.
I'm looking now
I'm still having trouble wrapping the 'form module' in my head, are you referring to the GuideBridge API by any chance?
I'm also going to have my colleague look into this as well buddy, hopefully we can get some more info on it.
Hey @MorisMonk , I'll have a chat with you on Monda...
From the below maven log entry it looks like that the apps package was successfully built but coiuldn't deploy to the AEM instance:
[INFO] Installing intranet.ui.apps (C:\home\development\intranet\intranet\ui.apps\target\intranet.ui.apps-1.1.6-SNAPSHOT.zip) to http://localhost:4502/crx/packmgr/ser...
This works for me:
1. Add below in main pom (You've already done that):
<dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>20.0</version></dependency>
2. In core pom:
Seems there isn't a way to directly access the request attributes in sightly and requires JS Use API. Here's a super short sample code to do just that: https://gist.github.com/gabrielwalt/a6a022ee65b3839d08bb4deb59211e57