この会話は、活動がないためロックされています。新しい投稿を作成してください。
この会話は、活動がないためロックされています。新しい投稿を作成してください。
I am using OOTB email for workflow (checked email option in dynamic participant step). The email contains link to localhost:4502/bin/... and I want that link to point towards dev/ qa etc environments. I assume that the link is coming from 'Day CQ Link Externalizer' local property.
After updating local value to author URL, it works fine but after each maven build the value in local gets overwritten. I have two issues here.
1. What's the actual meaning of having local here? Will it impact anything if I update it to author URL?
2. After each build, the local value gets overwritten to http://localhost:4502. I have file named 'com.day.cq.commons.impl.ExternalizerImpl.xml' under /apps/<my site>/config.dev/ and same under config.qa etc. Even if I update the file, the changes in local field are not getting reflected in /system/console/configMgr and they are overwritten with localhost link.
The file content in 'com.day.cq.commons.impl.ExternalizerImpl.xml' is:
解決済! 解決策の投稿を見る。
トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。
表示
返信
いいね!の合計
The local should always point to the instance. The reason is that AEM needs local for other internal operations.
A custom configuration allows you to add a new category, such as "production," "staging," or even external non-AEM systems such as "my-internal-webservice" and is useful to avoid hardcoding such URLs across different places in a project's codebase.
To point to author url, you should use the author entry.
More information about it can be found here:
Hope it helps !! 🙂
The local should always point to the instance. The reason is that AEM needs local for other internal operations.
A custom configuration allows you to add a new category, such as "production," "staging," or even external non-AEM systems such as "my-internal-webservice" and is useful to avoid hardcoding such URLs across different places in a project's codebase.
To point to author url, you should use the author entry.
More information about it can be found here:
Hope it helps !! 🙂
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
Hi,
you have to use Externalizer API for those links to convert based on osgi config.
Keep your config in the codebase.
com.day.cq.commons.impl.ExternalizerImpl.xml
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
jcr:primaryType="sling:OsgiConfig"
externalizer.domains= "[local https://localhost:4502,author https://author-sites.com,publish https://publish-sites.com]"/>
Java Code Example :
Externalizer externalizer = resolver.adaptTo(Externalizer.class);
if (null != externalizer && StringUtils.isNotBlank(domain)) {
if (ModeUtil.isAuthor()) {
externalLink = externalizer.authorLink(resolver, externalLink);
} else {
externalLink = externalizer.externalLink(resolver, domain, externalLink);
}
}
表示
返信
いいね!の合計