Disable OSGI Components & Bundles as part of Application Configuration


ACS AEM Commons OSGI Bundle and Component Disabler config allows to shut-down OSGI Components and Services by configuration. This feature allows OSGI Bundles and Components to be disabled as part of application configuration and these can be well managed for different environments using run modes config.

OSGI Component Disabler:
Define a sling:OsgiConfig under project config node:
Ex:
 /apps/poc/config/com.adobe.acs.commons.util.impl.ComponentDisabler
<?xml version="1.0" encoding="UTF-8"?>
jcr:primaryType="sling:OsgiConfig"
components="[pid1,pid2]"
/>
Snapshots below for reference:
Components would be an array of the OSGI component PIDs to disable. CRX and OSGI view of component disable configuration.







OSGI Bundle Disabler:
Bundles would be an array of the OSGI bundle symbolic names to disable.
Ex:
/apps/poc/config/com.adobe.acs.commons.util.impl.BundleDisabler
<?xml version="1.0" encoding="UTF-8"?>
jcr:primaryType="sling:OsgiConfig"
bundles="[bundle1,bundle2]"
/>
CRX and OSGI view of bundle disable configuration.



That's it and we are done with the bundle and component disabler configuration and can be utilized in any AEM specific need.

Comments

Post a Comment

Popular posts from this blog

AEM 6.3 | Apache Sling Content Disposition Filter | Hosting Static HTML in JCR

Image
In AEM 6.2 and 6.3, when we attempt to hit the static content such as (/content/site/static-page.html), it is treated as a binary download and does the same for all other file types(pdf,css, js, images) where r esponse header shows Content-Disposition as an attachment. In previous versions of AEM (6.1 and below),  com.day.cq.dam.core.impl.servlet.SafeBinaryGetServlet  was there to control response header to render page instead of download.  However from 6.2, this component is  deprecated and t he reason is Apache Sling Content Disposition Filter(org.apache.sling.security.impl.ContentDispositionFilter) took precedence and an intended change made in product from AEM 6.2 onward and was introduced as part of Sling Security Fix. Here we have steps to render static pages: Apache Sling Content Disposition Filter Configuration where static files needs to be added to meet requirements. Configuration can be reverted back to render static pages without adding it manually in OSGI by u
Read more

Image Component Customization - Image Size Restriction - Drag/Drop - Touch UI

Image
Customization of Image component or file upload resource type drag and drop from content/asset finder and restrict it to 1 MB or to any size. Step 1 : Create a AEM Image Component or use file upload resource type to drag and drop images in Touch UI dialog. Step 2 : Create Client library in your project application structure or inside component. Use categories as  cq.authoring.dialog or add extra clientlibs as needed . Step 3: Create a js file and add below piece of code which talks about file upload functions and accommodate for drag and drop behavior for coral classes from Content/Asset finder. As the page div for drag and drop creates on run time and becomes messy to retrieve the image size, hence a ajax call is used to get the image size post adapting resource to Asset. (function($, $document, ns) {     var FILE_UPLOAD_SELECTOR = ".cq-dialog .cq-FileUpload"; function imageSizeValidation(widget, elementName, imageSize, operation) {         if (widget &
Read more

Access OSGI ser­vice from Sightly WCMUsePojo | AEM 6.3

Create AEM 6.3 component making use of WCMUsePojo accessing OSGI Service. Step 1:  Create an interface name  OSGITestInterface.java  that will be implemented by service impl. public interface OSGITestInterface { String getOSGIName(); String getOSGIDesc(); String getOSGIuse(); String getOSGIData();  } Step 2:  Create a Interface Implementation class name  OSGITestInterfaceImpl.java import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.apache.felix.scr.annotations.Component; import org.apache.felix.scr.annotations.Service; @Component @Service public class OSGITestInterfaceImpl implements OSGITestInterface { Logger logger = LoggerFactory.getLogger(OSGITestInterfaceImpl.class); @Override public String getOSGIName() { return "Test Service"; } @Override public String getOSGIDesc() { return "AEM OSGI Service"; } @Override public String getOSGIuse() { return "OSGI Service data"; }        
Read more