I believe the issue with 'admin' user for IMS configs got fixed in the
release 6.5.5 here -
https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/service-pack/sp-release-notes.html
For AEM 6.5, ideally it should work fine if you install the package from
this document -
https://helpx.adobe.com/uk/experience-manager/kb/jaxws-webservice-calls-not-working-aem-65.html
if there is no class path issues due to embedding of jars in your
project. Package file
The experience fragment transformer is using the script
/libs/cq/experience-fragments/components/xfpage/body.nocloudconfigs.html
while exporting to target. You can remove the container class there by
overlaying in your custom template.
The markup while exporting to Target is based on
/libs/cq/experience-fragments/components/xfpage/body.nocloudconfigs.html
and the wrapper div's could be removed here.
I have created an experience fragment template(editable) by inheriting
from the "cq/experience-fragments/components/xfpage". However I am not
using scripts from the parent component in rendering. Everything looks
good in the final html page source while I preview in a disabled mode.
However when I export this to Target, I can see the content has got the
below client libraries present and I have found that this is coming from
the /libs/wcm/foundation/components/page/headlibs.html which is the
par...
The correct config is as following to override via
OSGioverrides="[[/content/test/en]de.joerghoh.cqdump.caconfig.workflow.CaConfigParticipantStepChooserConfig/approverGroup="osgi-approver"]"
Corrected the answer as the fix was to change the quotes after the
equals sign.
Hi Arun, I agree with you that both are different and the context of its
usage. However it is stated in sling documentation that we can override
the ca config values using osgi config in non prod environments. I've
tried that but I could not make it work in my local by using the above
config. My concern if the factory config I am using to override is
correct and if the value format is correct Best RegardsPaul
I am investigating the feasibility of overriding the Context Aware
values using OSGi configurations as stated in this document
https://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-override.html#override-via-osgi-configuration
Essentially this is for having different values based on run mode
configurations. Not for production environment. For example, I am taking
the a sample implementation created by Jörg here. If I want to overwrite
the value of...
