Skip navigation









Responsive Layouting is a mechanism for realizing responsive web design. This allows the user to create web pages that have a layout and dimensions dependent on the devices their users use.


This can be compared with the Mobile Web mechanisms, which use adaptive web design (primarily for the classic UI).

AEM realizes responsive layouting for your pages using a combination of mechanisms:

  • Layout Container component
    This component provides a grid-paragraph system to allow you to add and position components within a responsive grid. It can be used as the default parsys for your page and/or made available to authors in the component browser.

    • The default Layout Container component is defined under:
    • You can define layout containers:
      • As a component that the user can add to a page.
      • As the default parsys for the page.
      • Both.
        You can have the layout container as standard for the page, while allowing the user to add further layout containers within this; for example, to achieve column control.
  • Layouting Mode
    Once the layout container is positioned on your page you can use the Layouting mode to position content within the responsive grid.
  • Emulator
    This allows you to create and edit responsive websites that rearrange the layout according to device/window size by resizing components interactively. The user can then see how the content will be rendered using the Emulator.

AEM Responsive Grid

Whats New in 6.1: Layouting Mode

Change Viewpoer with Javascript

Viewport Resizer

Managing permissions (jackrabbit.accessmanager)

OAK – Access Control Management API

Difference between CQ 5.6.1 and AME6

AEM – Template in Details


Finding advanced information about your Blueprint and Livecopies status

1) http://host:port/content/path/to/bluprint/page.blueprint.json?&maxSize=500&advancedStatus=true&returnRelationships=true&msm%3Atrigger=ROLLOUT

2) http://host:port/content/path/to/bluprint/page.msm.json?_dc=1440692346666

continue reading on AEM-MSM-issues

Event Handling in CQ

Event filters

EventListener Sample

Performance tuning tips | 6.x

Repository inconsistency

Repository compaction

Oak TarMK Compaction

Apache Felix Gogo – Console Text Shell–rien-ne-va-plus—i-need-a-text-shell.html


Migration tips

Migration and Introduction

Maven Component Creator for Classic and Touch

Adobe Conversion Tool

Ben Thurley

RPG is the native language on the IBM as400 midrange server (aka iSeries, system i and now just “i”). In a recent project I had to find a way to call a number of RPG programs from a Java application. If you’re in this situation then there are a few options available.

  • PCML (the subject of this article)
  • SQL Stored procedure
  • Integrated web services server (IWS)

Stored procedure
One possibility is to write a SQL stored procedure using RPG which could be called from Java using JDBC. This option may not be viable depending on the parameters your program needs. A stored procedure is good for returning result sets of records but you can only return one and you can’t pass one in.

Integrated web services server (IWS)
If you want to quickly expose an RPG program as a web service then you might want to look at IWS

View original post 999 altre parole

Betaalbare Software Op Maat

This article elaborates on the usage of AngularJS and this in combination with AEM (Adobe Experience Manager). For this example, AEM version 6 has been used.

 From a functional point of view, the (rather basic) software component will allow to enter a JCR path and, by using AngularJS,  all the corresponding nodes will be automatically retrieved an displayed.

The UI form, being the main actor in our solution, would look the following.  It’s obvious the lay-out could be improved quite a bit but this is not really the focus of this tutorial.

AEM Angular UI

From a technical point of view, we’ll be using AngularJS (as mentioned before), jQuery and the DataTables jQuery plugin.


We first start with the HTML (view) and you’ll notice we did an effort to exclude all the business logic and to stick to the basic HTML.


As you can figure out from the…

View original post 481 altre parole

Java EE 7 (JSR 342) news

  • Annotated POJOs, which have proven to be the cornerstone of ease-of-development paradigm since Java EE 5, continue to rule the roost and further penetrate Java EE
  • Contexts and Dependency Injection (CDI) reputation of being the ‘magic glue’ has been taken to the next level – it’s now ‘default’ in Java EE 7 and its goal is to drive cohesiveness throughout the entire EE platform
  • JMS 2.0 (JSR 343) has been completely ‘revamped‘. A ‘new version’ of the API known as the ‘Simplified API‘ is more succinct, easy-to-use and will ensure that developers have to deal with ‘significantly lesser‘ amounts of ‘boilerplate‘ code
  • JAX-RS 2.0 (JSR 339) – The RESFTful API in Java EE 7 has been further enriched, including addition of a brand new ‘client’ side API, asynchronous capabilities, Servlet Filters and Interceptors
  • Java API for WebSocket (JSR 356) provides a ‘easy-to-use’ and powerful ‘high level’ abstraction for developers to write low latency, real-time and feature rich WebSocket driven applications
  • JSON Support – The Java API for JSON Processing (JSR 353) has finally ‘standardized’ JSON processing. No more ‘third party’ libraries required for dealing with JSON.
  • Concurrency Utilities (JSR 236) API now makes it possible to fire your own threads in Java EE 7 (forbidden prior to this) in a controlled/managed fashion
  • Batch Applications for Java Platform(JSR 352) – Brand new specification in Java EE 7, providing standard way to write efficient ‘batch processing‘ applications


JSR 356, Java API for WebSocket, specifies Java API that developers can use to integrate WebSockets into their applications — both on the server side as well as on the Java client side. Tyrus is the reference implementation for JSR 356.


Java API for JSON Processing


An Overview of Batch Processing in Java EE 7.0