Highlighted

AEM - Silly Developer Mistakes | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

967

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

967

Correct Answer

1.1K
kautuk_sahni
Community Manager

12-08-2020

BlogImage.jpg

AEM - Silly Developer Mistakes by Sreekanth Choudry Nalabotu

Abstract

1) When you see the property value modified or added is not reflecting in application, make sure you are editing the correct config file, eg. editing the s3 datastore config... there could be a possibility the file exists in install location author\crx-quickstart\install\org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.config, however the config values are picked from launchpad config author\crx-quickstart\launchpad\config\org\apache\jackrabbit\oak\plugins\blob\datastore\S3DataStore.config


2) When you see the property values not picked by application specified in the correct properties file, try to change the type for eg. in author\crx-quickstart\launchpad\config\org\apache\jackrabbit\oak\plugins\blob\datastore\S3DataStore.config specifying the value as Integer was not being picked up..

presignedHttpDownloadURIExpirySeconds=I"86404"

However changing it to string worked (removed I from value...)

presignedHttpDownloadURIExpirySeconds="86404"

Read Full Blog

AEM - Silly Developer Mistakes

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager