When we are trying to get/set context hub data to a store, it is throwing this exception Uncaught TypeError: ContextHub.getStore is not a functionwe are loading login.js (which has that code throwing exception ) is loaded after the context hub kernel JS this is exact line which throws this error Con...

thanks for response gaurav, I think i looked at it before but if you look at here Adobe Experience Manager Help | Injecting a DataSourcePool Service into an Adobe Experience Manager OSGi bundle  line # 115 of CustomerServiceImp.java, they are closing connection in finally block but not in other DB c...

To connect to mysql database, we defined JDBC pool service using which we are reading datasource and getting connection to read /write data.In the back java code finally block, we are doing connection.close(); when we are done with everything but now we are running into issue where its complaining a...

I dont understand why this thread was marked Answered though its pending further investigation by support or original issue for which this question was created does not resolved yet.

got it thanks

ok i saw this before but it does not answer my question why OOB email template host.prefix variable does not have correct value.Can you check with your team on this since its Adobe OOB email and back end class who call this template to trigger email.this will help me understand how $ {host.Prefix} v...

I agree, it work for me in Java or If I generate URL value using externalizer API in Java class and use it in email template as variable. But, it does not work for OOB workflow email template at location /libs/settings/workflow/notification/email/default/en.txtwhere its using $ {host.Prefix} for URL...

thanks smacdonald2008 for confirming. I will open one for this issue.

Yes we are using same approach using externalizer.domains to different mode , you can see that screenshot in thread main question.I dont have any issue using it with our custom notification where I am following exactly same as you mention and it work without any issue.The issue is only with OOB Work...

Thanks for checking internally. Meantime I will again go through this docs to confirm we are doing everything needed for 6.4