Article summary

 

Summary

Discusses how to create an AEM OSGi bundle that parses HTML using the JSOUP API.  

This article uses an Adobe Maven Archetype project to build an OSGi bundle. If you are not familiar with an Adobe Maven Archetype project, it is recommended that you read the following article: Creating your first AEM Service using an Adobe Maven Archetype project.

Digital Marketing Solution(s) Adobe Experience Manager (Adobe CQ)
Audience
Developer (Intermediate)
Required Skills
JavaScript, Java. OSGi, XML, HTML
Tested On Adobe Experience Manager 5.5, 5.6

Note:

You can download an AEM package that contains code and the OSGi bundle that are used in this article. Download the package and deploy using package manager. The purpose of this code is to show the communtiy these concepts in action. That is, it's to illustrate how to write an OSGi bundle that contains JSOUP functionality and parses HTML. This community code is for teaching purposes only and not meant to go into production as is.

You can view the sample community application by using the following URL: http://localhost:4502/cf#/content/Jsoup.html (assuming you deploy on author).

* HTMLParser_JSoup-1.0.zip
An AEM package that uses the JSOUP JAR
* jsoupBundle.zip
If there are not two OSGi bundles installed after installing the previous package, install this bundle manually in the Felix console (directions in this article). Unzip this ZIP file and install the JAR file - which is the OSGi bundle. This AEM example application requires two OSGi bundles, as shown in this illustration.
JSOUPBundles

Introduction

You can create a custom Adobe Experience Manager (AEM) HTML parser service that accepts HTML and parses it. By parsing HTML, you can retrieve HTML tag values. For example, consider the following HTML.

<div><p>Hello JSoup - this is now a CQ service.</p></div>

Once you pass this HTML to the custom AEM HTML parser service, you can get the value of the <p> tag, as shown in the following illustration. 

 

App


To create a custom Experience Manager HTML parser service, you can use the JSOUP library. That is, the application logic required to parse HTML is developed by using the JSOUP API. For information about this API, see: http://jsoup.org/.

The Java logic that parses HTML is implemented as an OSGi bundle that is built using Declarative Services (DS) and Maven. The OSGi bundle is a managed component, which means that the OSGi service container creates the OSGi instance.

Create an AEM application folder structure 

Create an AEM application folder structure that contains templates, components, and pages by using CRXDE Lite. 

CQAppSetup

An AEM folder structure

The following describes each application folder:

  • application name: contains all of the resources that an application uses. The resources can be templates, pages, components, and so on.
  • components: contains components that your application uses. 
  • page: contains page components. A page component is a script such as a JSP file. 
  • global: contains global components that your application uses.
  • template: contains templates on which you base page components. 
  • src: contains source code that comprises an OSGi component (this development article does not create an OSGi bundle using this folder). 
  • install: contains a compiled OSGi bundles container.
To create an AEM application folder structure:

 

  1. To view the CQ welcome page, enter the URL http://[host name]:[port] into a web browser. For example, http://localhost:4502.

  2. Select CRXDE Lite (if you are using AEM 5.6, click Tools from the left menu).

  3. Right-click the apps folder (or the parent folder), select Create, Create Folder.

  4. Enter the folder name into the Create Folder dialog box. Enter jsoup

  5. Repeat steps 1-4 for each folder specified in the previous illustration. 

  6. Click the Save All button.

Note:

You have to click the Save All button when working in CRXDE Lite for the changes to be made. 

Create a template 

You can create a template by using CRXDE Lite. A CQ template enables you to define a consistent style for the pages in your application. A template comprises of nodes that specify the page structure. For more information about templates, see https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/templates.html.

To create a template, perform these tasks:

  1. To view the CQ welcome page, enter the URL http://[host name]:[port] into a web browser. For example, http://localhost:4502.

  2. Select CRXDE Lite (if you are using AEM 5.6, click Tools from the left menu).

  3. Right-click the template folder (within your application), select Create, Create
    Template.

  4. Enter the following information into the Create Template dialog box:

    • Label: The name of the template to create. Enter templateJSoup.
    • Title: The title that is assigned to the template.
    • Description: The description that is assigned to the template.
    • Resource Type: The component's path that is assigned to the template and copied to implementing pages. Enter jsoup/components/page/templateJSoup.
    • Ranking: The order (ascending) in which this template will appear in relation to other templates. Setting this value to 1 ensures that the template appears first in the list.
  5. Add a path to Allowed Paths. Click on the plus sign and enter the following value: /content(/.*)?

  6. Click Next for Allowed Parents.

  7. Select OK on Allowed Children.

Create a render component that uses the template 

Components are re-usable modules that implement specific application logic to render the content of your web site. You can think of a component as a collection of scripts (for example, JSPs, Java servlets, and so on) that completely realize a specific function. In order to realize this functionality, it is your responsibility as a CQ developer to create scripts that perform specific functionality. For more information about components, see https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/components.html.

By default, a component has at least one default script, identical to the name of the component. To create a render component, perform these tasks:

  1. To view the CQ welcome page, enter the URL http://[host name]:[port] into a web browser. For example, http://localhost:4502.

  2. Select CRXDE Lite (if you are using AEM 5.6, click Tools from the left menu).

  3. Right-click /apps/jsoup/components/page, then select
    Create, Create Component.

  4. Enter the following information into the Create Component dialog box:

    • Label: The name of the component to create. Enter templateJSoup
    • Title: The title that is assigned to the component.
    • Description: The description that is assigned to the template.
  5.  Select Next for Advanced Component Settings and Allowed Parents.

  6. Select OK on Allowed Children.

  7. Open the templateJSoup.jsp located at: /apps/jsoup/components/page/templateJSoup/templateJSoup.jsp.

  8.  Enter the following JSP code.

<html>
<head>
<title>Hello World !!!</title>
</head>
<body>
<h1>Hello Custom HTML parser!!!</h1>
<h2>This page will parse HTML</h2>
</body>
</html>

Setup Maven in your development environment

You can use Maven to build an OSGi bundle that uses the JCR API and is deployed to Experience Manager. Maven manages required JAR files that a Java project needs in its class path. Instead of searching the Internet trying to find and download third-party JAR files to include in your project’s class path, Maven manages these dependencies for you.

You can download Maven 3 from the following URL:

http://maven.apache.org/download.html

After you download and extract Maven, create an environment variable named M3_HOME. Assign the Maven install location to this environment variable. For example:

C:\Programs\Apache\apache-maven-3.0.4

Set up a system environment variable to reference Maven. To test whether you properly setup Maven, enter the following Maven command into a command prompt:

%M3_HOME%\bin\mvn -version

This command provides Maven and Java install details and resembles the following message:

OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Note:

For more information about setting up Maven and the Home variable, see: Maven in 5 Minutes.

Next, copy the Maven configuration file named settings.xml from [install location]\apache-maven-3.0.4\conf\ to your user profile. For example, C:\Users\scottm\.m2\.

You have to configure your settings.xml file to use Adobe’s public repository. For information, see Adobe Public Maven Repository at http://repo.adobe.com/.

The following XML code represents a settings.xml file that you can use.

<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user, 
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in 
 |                 ${maven.home}/conf/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ~/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     | 
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are 
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->
    
    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   | 
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred 
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     -->
  </mirrors>
  
  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is 
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a 
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
  <profiles>
    <!-- profile
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>
        <repository>
          <id>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</url>
          <layout>default</layout>
          <snapshotPolicy>always</snapshotPolicy>
        </repository>
      </repositories>
    </profile>
    -->

    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |   
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
  

<profile>

                <id>adobe-public</id>

                <activation>

                    <activeByDefault>true</activeByDefault>

                </activation>

                <repositories>

                  <repository>

                    <id>adobe</id>

                    <name>Nexus Proxy Repository</name>

                    <url>http://repo.adobe.com/nexus/content/groups/public/</url>

                    <layout>default</layout>

                  </repository>

                </repositories>

                <pluginRepositories>

                  <pluginRepository>

                    <id>adobe</id>

                    <name>Nexus Proxy Repository</name>

                    <url>http://repo.adobe.com/nexus/content/groups/public/</url>

                    <layout>default</layout>

                  </pluginRepository>

                </pluginRepositories>

            </profile>

</profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

Create an Experience Manager archetype project

You can create an Experience Manager archetype project by using the Maven archetype plugin. In this example, assume that the working directory is C:\AdobeCQ.  

Maven

 

To create an Experience Manager archetype project, perform these steps:

  1. Open the command prompt and go to your working directory (for example, C:\AdobeCQ).

  2. Run the following Maven command:

    mvn archetype:generate -DarchetypeRepository=https://repo.adobe.com/nexus/content/groups/public/ -DarchetypeGroupId=com.day.jcr.vault -DarchetypeArtifactId=multimodule-content-package-archetype -DarchetypeVersion=1.0.2 -DgroupId=com.adobe.cq.jsoup -DartifactId=jsoupservice -Dversion=1.0-SNAPSHOT -Dpackage=com.adobe.cq.jsoup -DappsFolderName=myproject -DartifactName="My Project" -DcqVersion="5.6.1" -DpackageGroup="My Company"

  3. When prompted for additional information, specify Y.

  4. Once done, you will see a message like:
    [INFO] Finished at: Wed Mar 27 13:38:58 EDT 2013
    [INFO] Final Memory: 10M/184M

  5. Change the command prompt to the generated project. For example: C:\AdobeCQ\jsoupservice. Run the following Maven command:
    mvn eclipse:eclipse

After you run this command, you can import the project into Eclipse as discussed in the next section.

Add Java files to the Maven project using Eclipse

To make it easier to work with the Maven generated project, import it into the Eclipse development environment, as shown in the following illustration. 

Exclipse

The next step is to add Java files to the com.adobe.cq.jsoup package. Add the following Java files to this package:

1. A Java interface named HTMLService.
2. A Java class named HTMLServiceImpl that implements the HTMLService interface.

HTMLService interface

The following code represents the HTMLService interface. This interface contains a method signature named processHTML. The implementation logic for this method uses the JSoup API to parse the HTML that is passed to this method. 

The following Java code represents the HTMLService interface. 

package com.adobe.cq.jsoup;

public interface HTMLService {
	
	public String processHTML(String html); 

}

HTMLServiceImpl interface

The HTMLServiceImpl class uses the following Apache Felix SCR annotations to create the OSGi component:

  • @Component – defines the class as a component
  • @Service - defines the service interface that is provided by the component

Within the processHTML method, parse the HTML and retrieve the value of the <P> tag that is located in the HTML that is passed to this method. (In this example, the HTML ithat is parsed is defined in the JSP that invokes this service. This is shown later in this development article.)

The following Java code represents the processHTML method.

@Override
public String processHTML(String html) {
		
String myPara="" ; 
 try
{
    Document doc = Jsoup.parseBodyFragment(html);
    Element body = doc.body();

    //Get the value of the P tag and return it	
    Elements links = body.getElementsByTag("p");
    for (Element link : links) {
    	myPara = link.text();
       }
    return myPara ; 
}
catch(Exception e)
{
	e.printStackTrace();
}
return null; 
}

The following Java code represents the entire HTMLServiceImpl class. 

package com.adobe.cq.jsoup;


import org.jsoup.Jsoup;
import org.jsoup.nodes.*;
import org.jsoup.select.*;

import org.apache.felix.scr.annotations.Properties;
import org.apache.felix.scr.annotations.Property;
import org.apache.felix.scr.annotations.Reference;
import org.apache.felix.scr.annotations.Reference;
import org.osgi.service.component.ComponentContext;

 

import org.apache.felix.scr.annotations.Activate;
import org.apache.felix.scr.annotations.Reference;
import org.osgi.service.component.ComponentContext;
import org.apache.felix.scr.annotations.Component;
import org.apache.felix.scr.annotations.Service;  

 
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
 

//This is a component so it can provide or consume services
@Component
  
@Service
public class HTMLServiceImpl implements HTMLService {

	/** Default log. */
	protected final Logger log = LoggerFactory.getLogger(this.getClass());
	
	@Override
	public String processHTML(String html) {
		
		String myPara="" ; 
		try
		{
			Document doc = Jsoup.parseBodyFragment(html);
	        Element body = doc.body();

	        //Get the value of the P tag and return it	
	        Elements links = body.getElementsByTag("p");
	        for (Element link : links) {
	        	myPara = link.text();
	           }
	        return myPara ; 
		}
		catch(Exception e)
		{
			e.printStackTrace();
		}
		return null; 
		
		}

}

Add the JSOUP JAR file to Experience Manager

Add the JSOUP JAR file to Experience Manager within an OSGi bundle. The reason is because the processHTML method uses the JSoup API to parse the HTML that is passed to the method. If you do not add this class to Experience Manager, then you are unable to place the OSGi bundle that contains the HTMLService interface into an Active state.

To add the JSOUP JAR to Experience Manager, add it to a bundle  and then deploy the bundle, as discussed in this section. First, download the JSOUP JAR from the URL shown at the beginning of this development article.

To create an OSGi bundle fragment that contains the JSOUP API, perform these tasks:

  1. Start Eclipse (Indigo). The steps below have been tested on Eclipse Java EE IDE for Web Developers version Indigo Service Release 1.

  2. Select File, New, Other.

  3. Under the Plug-in Development folder, choose Plug-in from Existing JAR Archives. Name your project jsoupBundle.

  4. In the JAR selection dialog, click the Add external button, and browse to the JSOUP JAR file that you downloaded.

  5. Click Next.

  6. In the Plug-in Project properties dialog, ensure that you check the checkbox for Analyze library contents and add dependencies.

  7. Make sure that the Target Platform is the standard OSGi framework.

  8. Ensure the checkboxes for Unzip the JAR archives into the project and Update references to the JAR files are both checked.

  9. Click Next, and then Finish.

  10. Click the Runtime tab.

  11. Make sure that the Exported Packages list is populated.

  12. Make sure these packages have been added under the Export-Package header in MANIFEST.MF. Remove the version information in the MANIFEST.MF file. Version numbers can cause conflicts when you upload the OSGi bundle.

  13. Also make sure that the Import-Package header in MANIFEST.MF is also populated, as shown here (notice that Export-Package is org.jsoup).

    Bundle-ManifestVersion: 2
    Bundle-Name: JSoupOSGi
    Bundle-SymbolicName: JSoupOSGi
    Bundle-Version: 1.0.0
    Export-Package: org.jsoup,
    org.jsoup.examples,
    org.jsoup.helper,
    org.jsoup.nodes,
    org.jsoup.parser,
    org.jsoup.safety,
    org.jsoup.select
    Bundle-RequiredExecutionEnvironment: JavaSE-1.6

  14. Save the project.

  15. Build the OSGi bundle by right-clicking the project in the left pane, choose Export, Plug-in Development, Deployable plug-ins and fragments, and click Next.

  16. Select a location for the export (C:\TEMP) and click Finish. (Ignore any error messages).

  17. In C:\TEMP\plugins, you should now find the OSGi bundle.

  18. Login to the Apache Felix Web Console at http://server:port/system/console/bundles (default admin user = admin with password= admin).

  19. Sort the bundle list by Id and note the Id of the last bundle.

  20. Click the Install/Update button.

  21. Check the Start Bundle checkbox.

  22. Browse to the bundle JAR file you just built. (C:\TEMP\plugins).

  23. Click Install.

  24. Click the Refresh Packages button.

  25. Check the bundle with the highest Id.

  26. Your new bundle should now be listed with the status Active.

  27. If the status is not Active, check the error.log for exceptions. If you get “org.osgi.framework.BundleException: Unresolved constraint” errors, check the MANIFEST.MF for strict version requirements which might follow: javax.xml.namespace; version=”3.1.0”

  28. If the version requirement causes problems, remove it so that the entry looks like this: javax.xml.namespace.

  29. If the entry is not required, remove it entirely.

  30. Rebuild the bundle.

  31. Delete the previous bundle and deploy the new one.

Modify the Maven POM file 

Modify the POM files to successfully build the OSGi bundle. In the POM file located at C:\AdobeCQ\customer\bundle, add the following dependencies.

  • org.apache.felix.scr
  • org.apache.felix.scr.annotations
  • org.jsoup.select
  • org.apache.sling

The following XML represents this POM file.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd ">
    <modelVersion>4.0.0</modelVersion>
    <!-- ====================================================================== -->
    <!-- P A R E N T P R O J E C T D E S C R I P T I O N -->
    <!-- ====================================================================== -->
    <parent>
        <groupId>com.adobe.cq.jsoup</groupId>
        <artifactId>jsoupservice</artifactId>
        <version>1.0-SNAPSHOT</version>
    </parent>

    <!-- ====================================================================== -->
    <!-- P R O J E C T D E S C R I P T I O N -->
    <!-- ====================================================================== -->

    <artifactId>jsoupservice-bundle</artifactId>
    <packaging>bundle</packaging>
    <name>Training Package Bundle</name>

    <!-- ====================================================================== -->
    <!-- B U I L D D E F I N I T I O N -->
    <!-- ====================================================================== -->
    <build>

        <plugins>
            <plugin>
                <groupId>org.apache.felix</groupId>
                <artifactId>maven-scr-plugin</artifactId>
                <executions>
                    <execution>
                        <id>generate-scr-descriptor</id>
                        <goals>
                            <goal>scr</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <plugin>
                <groupId>org.apache.felix</groupId>
                <artifactId>maven-bundle-plugin</artifactId>
                <extensions>true</extensions>
                <configuration>
                    <instructions>
                        <Bundle-SymbolicName>com.adobe.cq.jsoup.jsoupservice-bundle</Bundle-SymbolicName>
                    </instructions>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.sling</groupId>
                <artifactId>maven-sling-plugin</artifactId>
                <configuration>
                    <slingUrl>http://${crx.host}:${crx.port}/apps/custom-service/install</slingUrl>
                    <usePut>true</usePut>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <dependencies>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>org.osgi.compendium</artifactId>
        </dependency>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>org.osgi.core</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.felix</groupId>
            <artifactId>org.apache.felix.scr.annotations</artifactId>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
        </dependency>
         
          
        <dependency>
         <groupId>org.apache.felix</groupId>
   
         <artifactId>org.osgi.core</artifactId>
   
         <version>1.4.0</version>
      </dependency>
      
      
       <dependency>
            <!-- jsoup HTML parser library @ http://jsoup.org/ -->
            <groupId>org.jsoup</groupId>
            <artifactId>jsoup</artifactId>
            <version>1.7.3</version>
        </dependency>
      
    </dependencies>
</project>

Build the OSGi bundle using Maven

Build the OSGi bundle by using Maven. To build the OSGi component by using Maven, perform these steps:

  1. Open the command prompt and go to the C:\AdobeCQ\jsoupservice folder.
  2. Run the following maven command: mvn clean install.
  3. The OSGi component can be found in the following folder: C:\AdobeCQ\jsoupservice\bundle\target. The file name of the OSGi component is jsoupservice-bundle-1.0-SNAPSHOT.jar.
  1. Open the command prompt and go to the C:\AdobeCQ\jsoupservice folder.

  2. Run the following maven command: mvn clean install.

  3. The OSGi component can be found in the following folder: C:\AdobeCQ\jsoupservice\bundle\target. The file name of the OSGi component is jsoupservice-bundle-1.0-SNAPSHOT.jar.

Note:

Remove the version numbers from the Manifest file located in the jsoupservice-bundle-1.0-SNAPSHOT.jar file. You can find the Manifest file at this location: jsoupservice-bundle-1.0-SNAPSHOT.jar\META-INF.

Deploy the bundle to Experience Manager

Once you deploy the OSGi bundle, you are able to invoke the processHTML method defined in the HTMLServiceImpl class (this is shown later in this development article). After you deploy the OSGi bundle, you are able to see it in the Apache Felix Web Conole.

felix

Deploy the OSGi bundle by performing these steps:

  1. Login to the Apache Felix Web Console at http://server:port/system/console/bundles (default admin user = admin with password= admin).

  2. Click the Bundles tab, sort the bundle list by Id, and note the Id of the last bundle.

  3. Click the Install/Update button.

  4. Browse to the bundle JAR file you just built using Maven. (C:\AdobeCQ\jsoupservice\bundle\target).

  5. Click Install.

  6. Click the Refresh Packages button.

  7. Check the bundle with the highest Id.

  8. Click Active. Your new bundle should now be listed with the status Active.

  9. If the status is not Active, check the error.log for exceptions.

Note:

The name of the service defined within the OSGi bundle is com.adobe.cq.jsoup.HTMLService

Modify the Client JSP to invoke the processHTML method 

Create a HTMLService object by using the sling.getService method. After you create a HTMLService object, you can invoke the processHTML method exposed by the service. You pass a string value to this method that represents the HTML to parse. The following code represents the updated templateJSoup.jsp

<%@include file="/libs/foundation/global.jsp"%>
<%@ page import="org.apache.sling.commons.json.io.*,com.adobe.cq.*" %>
<h1>AEM Custom HTML Parser service</h1>
<%
 
com.adobe.cq.jsoup.HTMLService customHTMLService = sling.getService(com.adobe.cq.jsoup.HTMLService.class);

 

%>
 
<h2>The AEM Custom HTML Parser service parses this HTML: <code><div><p>Hello JSoup - this is now a CQ service.</p></div></code></h2>
<h3><%= "Value of the P tag is: " +customHTMLService.processHTML("<div><p>Hello JSoup - this is now a CQ service.</p></div>")%></h3>

Modify the templateJSoup.jsp file by performing these tasks:

  1. To view the welcome page, enter the URL: http://[host name]:[port] into a web browser. For example, http://localhost:4502.

  2. Select CRXDE Lite. (If you are using AEM 5.6, click Tool in the left menu).

  3. Double-click apps/jsoup/components/page/templateJSoup/templateJSoup.jsp.

  4. Replace the JSP code with the new code shown in this section.

  5. Click Save All.

Create an Experience Manager web page that parses HTML 

The final task is to create a site that contains a page that is based on the templateJSoup (the template created earlier in this development article). When the page is opened, the HTML is passed to the custom AEM HTML parser service. The parsed value is returned and displayed in the web page.  

Create an Experience Manager web page that queries and persists data from the AEM JCR:

  1. Go to the welcome page at http://[host name]:[port]; for example, http://localhost:4502.

  2. Select Websites. (If you are using AEM 5.6, click Tools from the menu on the left.)

  3. From the left hand pane, select Websites.

  4. Select New Page.

  5. Specify the title of the page in the Title field.

  6. Specify the name of the page in the Name field.

  7. Select templateJSoup from the template list that appears. This value represents the template that is created in this development article. If you do not see it, then repeat the steps in this development article. For example, if you made a typing mistake when entering in path information, the template will not show up in the New Page dialog box.

  8. Open the new page that you created by double-clicking it in the right pane. The new page opens in a web browser. You should see a page similar to the illustration shown at the beginning of this development article.

See also

Congratulations, you have just created an AEM OSGi bundle by using an Adobe Maven Archetype project. Please refer to the AEM community page for other articles that discuss how to build AEM services/applications by using an Adobe Maven Archetype project.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy