I'm trying to create a live copy of a page but in a java class in my Core bundle. I'm struggling to find the correct java classes to do this. So far I have found the TemplateRolloutService in com.adobe.cq.social.blueprint.api which looks the most promosing although not sure why it is in the social package!
However I can't find any documentation, I have got the unobfuscated JAR from Daycare but the class has no javaDoc and the input params to the methods are not named helpfully in my decompiler e.g.
Page createLiveCopy(SlingRepository var1, ResourceResolver var2, RolloutManager var3, String var4, String var5, String var6, String var7, ValueMap var8) throws OperationException, RepositoryException, WCMException;
So two questions really:
Solved! Go to Solution.
Hi Sutty,
Apart from legal terms, Decompile is good and bad . If you are reverse engineering some features which is legacy & no support then only go with decompile otherwise you end up wrong implementation which will break later. So avoid decompile.
missingPage@Delete:<true|false>
excludeSubPages@Delete:<true|false>
destPath:<target_path>
title:<Live_copy_title_name>
label:<Live_copy_label_name>
srcPath:<source_path>
shallow@Delete:<true|false>
cq:rolloutConfigs:<List_of_rolloutconfig_to_add>
cq:rolloutConfigs@Delete:<List_of_rolloutconfig_to_remove_in_case_of_updation_only>
If you think above approach can be made easy then log an issue with adobe official support team.
Best way to understand api is
Spend time on official api documentation. https://docs.adobe.com/docs/en/aem/6-2/develop/ref.html
Use request analyzer & rollout using the UI. Then see the flow in request analyzer. https://sling.apache.org/documentation/bundles/request-analysis.html
Post in forums OR stackoverflow. Reach out to official support team.
Avoid Shortcuts like Decompile to get things quickly and end up with non api usage & legal trap.
Thanks,
Views
Replies
Total Likes
Hi Sutty,
Apart from legal terms, Decompile is good and bad . If you are reverse engineering some features which is legacy & no support then only go with decompile otherwise you end up wrong implementation which will break later. So avoid decompile.
missingPage@Delete:<true|false>
excludeSubPages@Delete:<true|false>
destPath:<target_path>
title:<Live_copy_title_name>
label:<Live_copy_label_name>
srcPath:<source_path>
shallow@Delete:<true|false>
cq:rolloutConfigs:<List_of_rolloutconfig_to_add>
cq:rolloutConfigs@Delete:<List_of_rolloutconfig_to_remove_in_case_of_updation_only>
If you think above approach can be made easy then log an issue with adobe official support team.
Best way to understand api is
Spend time on official api documentation. https://docs.adobe.com/docs/en/aem/6-2/develop/ref.html
Use request analyzer & rollout using the UI. Then see the flow in request analyzer. https://sling.apache.org/documentation/bundles/request-analysis.html
Post in forums OR stackoverflow. Reach out to official support team.
Avoid Shortcuts like Decompile to get things quickly and end up with non api usage & legal trap.
Thanks,
Views
Replies
Total Likes
Hi MC Stuff,
Please, could you provide the equivalent class or method for AEM6.3 Java API ?
Thanks
Views
Replies
Total Likes
I would open a support ticket against the AEM Docs and ask if this API is still applicable:
com.day.cq.wcm.msm.api (Adobe CQ 5.6.1 Java Documentation 5.6.1 API)
In a lot of cases - they Java APIs do not change from version to version. This should be clear in the docs.
Views
Likes
Replies