Thursday 28 May 2015

Adobe Experience Manager 6.1

Adobe Experience Manager 6.1 is now live.




 For information, see the AEM 6.1 documentation.

For a list of Whats New, see the 'What's New in AEM 6.1' section in the Release Notes. This is a great starting point to learn about new features.


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Creating Adobe Experience Manager Components that use Standard Tag Libraries

You can create Adobe Experience Manager (AEM) components that use the JSP Standard Tag Library (JSTL). JSP tags let you integrate  core functionality common to applications. For example, using JSP tags, you can perform tasks such as iterating through collections, parsing XML documents, performing SQL operations, and so on. For more information, see JSP - Standard Tag Library.

This development article walks you through how to build an AEM component that uses JSP tags to display information, including an image from the AEM DAM. The following illustration shows the output of an AEM component that uses JSP tags.


To read this development article, click https://helpx.adobe.com/experience-manager/using/jstl.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Wednesday 20 May 2015

Packaging Adobe Experience Manager 6 applications

You can package an Adobe Experience Manager (AEM) 6 application that contains an OSGi bundle by using Package Manager. Once an application (including the OSGi bundle) is placed into a package, you can deploy it to another AEM instance. If your CQ package does not include the OSGi bundle, then the application will not successfully work when deployed to the new AEM instance.

This article discusses how to create AEM packages using AEM 6 Touch UI, as shown in this illustration.


This article walks you through how to package an AEM 6 application using the Touch UI. TO read this development article, click https://helpx.adobe.com/experience-manager/using/packaging-aem6-applications.html.

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner

About the Author

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 16 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.
TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.


Tuesday 12 May 2015

May session of AEM Ask the Community Experts

Join Lokesh BS (a top AEM community contributor) and Scott Macdonald for a discussion about Adobe Experience Manager and Sling. This session will cover in depth sling concepts such as Sling Selectors, Default Sling Post Servlet, Sling Models, and the Sling API.
By attending this session you will gain a deeper understanding of Sling concepts and how to use Sling while developing Experience Manager projects.


To watch the playback of this session, go to: http://bit.ly/1HHiqsb.  
The password is SlingAEM.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Thursday 7 May 2015

Using Event Handlers in Adobe Experience Manager Touch UI Components

When developing Adobe Experience Manager (AEM) Touch UI components, handling events is an important task. In AEM 6, the Touch UI APIs do not have event handler methods. For information about the AEM Touch UI APIs, see Granite UI documentation.

As a result, to handle events, use DOM supported events. You can use JQuery to handle events. For example, the following code represents the event handler that is invoked when the Touch UI dialog is opened:


    $document.on("dialog-ready", function() {
        $(window).adaptTo("foundation-ui").alert("Open", "Dialog now open, event [dialog-ready]");
    });

This event handler produces an alert message box that appears when the Touch UI dialog is opened, as shown in the following illustration.


This development article discusses how to create a Touch UI component that uses event handlers. To read this development article, click https://helpx.adobe.com/experience-manager/using/creating-touchui-events.html

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel



Tuesday 5 May 2015

Working with Sling Models in Adobe Experience Manager

You can work with Sling Models when developing with Adobe Experience Manager (AEM). That is, when developing an AEM project,  you can define a model object, which is a Java object that is mapped to a Sling object, typically resources, but also request objects. A Sling Model is implemented as an OSGi bundle.

A Java class located in the OSGi bundle is annotated with @Model and the adaptable class. The data members (Fields) use the @Inject annotation. Consider the following Java class.

package org.kalyan.poc.sling.models;

import javax.inject.Inject;

import org.apache.sling.api.resource.Resource;
import org.apache.sling.models.annotations.Model;

@Model(adaptables = Resource.class)
public class UserInfo {
@Inject
private String firstName;
@Inject
private String lastName;
@Inject
private String technology;

public String getFirstName() {
return firstName;
}
public String getLastName() {
return lastName;
}
public String getTechnology() {
return technology;
}

}

As you can see the @Model annotation is used. Likewise, each data member in the UserInfo class is annotated using @Inject.  For more information about Sling Models, see Sling Models

This article walks you through creating an AEM application that uses Sling Models. To read this development article, click https://helpx.adobe.com/experience-manager/using/sling_models.html



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel