Are you talking about creating editable templates dynamically? It sounds
like it from "create a template dynamically using the sling model
response"The best practice is to create an Editable Template (or more),
create AEM Components using Sling Models, then in your Editable
Template(s) - you set the policy the drives which components are allowed
to be used in that given template.Sling Models are used to create a
given component - not Editable Templates.You should follow the WEEKEND
If you do not know how to create a custom workflow step, or use an AEM
API within a workflow, or other workflow-related tasks - such as using
an OR split - see this DEV doc - Adobe Experience Manager Help |
Invoking an Adobe Experience Manager Custom 6.4 Workflow from a web page
Do you mean if your resource is the Payload of the workflow? Typically
to perform operations on a resource via a workflow - you can use the AEM
APIS. You would use the Workflow API to create a custom workflow step.
Then you can use other APIS - ie - Asset API if the payload was an
Did you use this:You can run the AEM application from IntelliJ. To run
the application, you have start AEM in debug mode by using the following
command from the folder where the AEM quick start is located:java
This is not a specific AEM OOTB use case. You need to write a custom
service perhaps using Java/OSGi bundle:
https://www.vogella.com/tutorials/RSSFeed/article.html AEM is a
development stack and you can pretty much use Java to make develop
solutions to meet your business requirements.
Are you trying to use a custom Java API. If so - you need to wrap that
JAR that exposes the Java package into an OSSi bundle and deploy to AEM.
Remember that when building an OSGi bundle that contains a Java API -
you need to ensure 2 things:1 - you reference the API in the POM (which
you did)2 - you need to make sure there is a deployed OSGi bundle in the
AEM Service container that exposes the given Java package - sounds like
this is not the case).
Wrap the Driver file into an OSGi bundle and deploy. This is shown in
many articles:Adobe Experience Manager Help | Querying MySQL data using
an Adobe Experience Manager 6.4 DataSourcePoolAs Joerg has pointed out -
referencing the dependency in the POM file only ensures the build is
created successfully - it does not place the driver file into an OSGi
bundle and deploy to AEM.