@cqbeginner Well, firstly, the third-party application needs to get access to communicate with your author instance. And secondly, the default behavior to successfully make a call to the AEM OOTB asset's API is when you are an authenticated user. As a test, open API development tool such as POSTMAN ...

Hello @Sam205505050,Your configuration looks correct, The following example /renders section distributes render requests equally among two AEM instances (Adobe documentation) : /renders { /myFirstRenderer { /hostname "https://publish-1.com" /port "8443" } /mySecondR...

@BhanuJain,In my opinion, It really depends on what your companies long term vision for technology. Do you see your company moving more towards ReactJS or Angular. You should gather some research online and discuss the pros and cons for ReactJS vs Angular with your team, and together, agree with you...

@Shwetha1994,Take a look at these two articles:https://www.nextrow.com/blog/adobe-experience-manager/a-comprehensive-guide-on-vanity-url-in-aemhttps://www.nextrow.com/blog/adobe-experience-manager/vanity-urls-in-aem-part-2And I don't think the out of the box vanity URL will work with selectors, it o...

@Kailash07 Although I've never extended the HTML library manager, I applied a manual approach. I can shed some light on the manual approach I've seen being used in production.I understand where you are coming from. While embedding the entire client library will have pros and cons, ultimately you wan...

@Jai1122 You should always continue to serve the old code deployment via cached pages until after another code deployment is complete. Once the new code deployment is complete, then you can manually flush the cache to serve new initiatives to the end-user. You can automate this, anthoer option is th...

You can just go to parent pom.xml, and comment out the "dispatcher.cloud" module. Next, mvn clean install again. Since you do not have the correct profile, head into ui.apps/target/.*.zip, and upload it manually into AEM using the package manager. Your build logs looks fine, except for the dispatche...

Try again after making your Sling Model more simple. Change to :@Model(adaptables = { SlingHttpServletRequest.class, Resource.class }, defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL) public class PageModel implements Page { } If this doesn't work, try to remo...

@Deleted Account,It says:aem-guides-wknd.all-0.0.6.zip: AEM as a Cloud Service, the default buildaem-guides-wknd.all-0.0.6-classic.zip: AEM 6.5.4+, AEM 6.4.8+ This is built with the additional profile classic and uses v6.4.4 of the uber jar.If you are running an AEM instance on your local developmen...

@Nitin_laad do you have the RunWith annotation set? @RunWith(MockitoJUnitRunner.class) public class ComponentTest { @Rule public final AemContext context = new AemContext(ResourceResolverType.JCR_MOCK); private Component component; @Test public void itShouldNotBeNull() { ...