Examples of the things that can be done with the different technologies that compose AEM
The project's base structure was built with aem-project-archetype
- A simple custom service.
- A simple periodic task with fixed time period.
- A custom event listener.
- A simple job.
- Example of how to get service references from a component.
- Example of how to inject properties in a Sling Model.
- Example of an OSGi configuration node.
- Example of a configuration file.
- Example of a bundle activator.
- A simple component.
- Example of mapping to be able to access the JCR repository.
- Example of a 'path' servlet.
- Example of how to adapt a Sling Model
- Example of event handler that modifies a resource.
- Example of Searches using SQL and JQOM
- Example of a polling service.
- Example of a workflow process step.
- Example of page creator (importer) servlet.
- Example of page creator (importer) servlet that uses a csv file.
- Example of hobbes functional tests.
- Example of servlet used to import content.
- Example of component with default content.
- Example of text component with custom configs.
- Example of how to add css styles for a specific mode.
- Example of how to ue hooks to customize edit dialogs.
- Example of how to read values form multifield.
- Example of how to read values form a multifield that uses a widget.
- Example of how to construct a custom color picker widget.
- Example of a design dialog for the color text component.
- Example of how to use a service configuration factory.
- Example of how to inject a service in a Sling Model.
- Example of how to use a Sling Model as a datasource for a dropdown in an edit dialog.
- Example of Sling Mappings.
The main parts of the template are:
- core: Java bundle containing all core functionality like OSGi services, listeners or schedulers, as well as component-related Java code such as servlets or request filters.
- ui.apps: contains the /apps (and /etc) parts of the project, ie JS&CSS clientlibs, components, templates, runmode specific configs as well as Hobbes-tests
- ui.content: contains sample content using the components from the ui.apps
- ui.tests: Java bundle containing JUnit tests that are executed server-side. This bundle is not to be deployed onto production.
- ui.launcher: contains glue code that deploys the ui.tests bundle (and dependent bundles) to the server and triggers the remote JUnit execution
To build all the modules run in the project root directory the following command with Maven 3:
mvn clean install
If you have a running AEM instance you can build and package the whole project and deploy into AEM with
mvn clean install -PautoInstallPackage
Or to deploy it to a publish instance, run
mvn clean install -PautoInstallPackagePublish
Or alternatively
mvn clean install -PautoInstallPackage -Daem.port=4503
Or to deploy only the bundle to the author, run
mvn clean install -PautoInstallBundle
There are three levels of testing contained in the project:
-
unit test in core: this show-cases classic unit testing of the code contained in the bundle. To test, execute:
mvn clean test
-
server-side integration tests: this allows to run unit-like tests in the AEM-environment, ie on the AEM server. To test, execute:
mvn clean verify -PintegrationTests
-
client-side Hobbes.js tests: JavaScript-based browser-side tests that verify browser-side behavior. To test:
in the browser, open the page in 'Developer mode', open the left panel and switch to the 'Tests' tab and find the generated 'MyName Tests' and run them.
The project comes with the auto-public repository configured. To setup the repository in your Maven settings, refer to:
http://helpx.adobe.com/experience-manager/kb/SetUpTheAdobeMavenRepository.html