@annkitaaggarwal,You can achieve this by using custom CSS. Target the first tr HTML block element with table tr:first-child, and change the background color to something like grey. Example below is a screenshot of what the table styles will look like. At the bottom of this response, you will find so...

For JUNIT4 example, you can checkout this reference here, https://sourcedcode.com/blog/aem/aem-sling-servlet-osgi-r7-by-resource-type-unit-test-junit-4-with-examples 

@GS04 you can follow this tutorial on how to setup the content fragment models structure, https://www.youtube.com/watch?v=-Hn3UDJMc98 After creation of your content fragments model structure, you should be able to find the created-resources under the /conf/my-site/* folder.

You can achieve this by writing your own Event Handlers, Event Listeners, or Workflow Launchers https://aem.redquark.org/2018/10/day-14-eventing-in-aem.html 

@chun-pin,You can utilise the granite/ui/components/coral/foundation/include, simply create one configuration, for example, margins, within your common namespace folder, as /apps/mybrand/dialogs/content/common/fields,and re-use them across your AEM project.  Here's an example of how we identified on...

Can you share the TouchUI Dialogue .content.xml please; 

@SupportMember,I am afraid after when a new bundle have been deployed, the JVM is still running, which means that these threads are not closed. Restart your AEM to close all your open threads.@Asutosh_Jena_'s recommendation try-with-resource trick introduced in Java 7  will ensure that the session i...

Excellent, im glad that it worked out; unfortunately, there is no out of the box solution to fix this cause. A solution with javascript is just too troublesome. 

Installation of a new paraformat option, and using Java Backend, Sling Model, we can text-transform the output, so that your Sightly HTL can render the output Html as expected. For the full tutorial you can find it here. https://sourcedcode.com/blog/aem/aem-richtext-remove-p-tag-removesingleparagrap...

I suggest you to write all the business logic in the sling model itself. So that you would only need to call the getter from your Sling Model, and the transformed url will be the final string that you will be using for the Url output.