コミュニティアチーブメントバーを展開する。

kevingtan
kevingtan
オフライン
タイプ
  • すべて
  • 質問
  • ディスカッション
  • アイデア
  • ブログ
ユーザー投稿による絞り込み
  • @Asutosh_Jena_, Thanks! I see the dispatcher takes the publisher as the first priority. It is supposed to get the local contents first, but it turns otherwise.Here is the log, where n_t.html is the file directly created in the cache folder: [Thu Mar 18 10:17:36 2021] [D] [40151(140249987221472)] Fou...

    タイプ

    質問

    表示

    1.7K

    いいね!

    0

    返信

    0
  • The log tells something pretty much as expected. The dispatcher skips itself and goes directly to the publisher to request the file.I am showing the two different environments so you can see the difference.  Case 1, the problematic one:I shut down the publisher. I created a file "n_t.html" directly ...

    タイプ

    質問

    表示

    1.7K

    いいね!

    0

    返信

    0
  • Thanks for your help! Well, I created a file directly under the cache folder, and expect the dispatcher can serve it to the end users. Looks like it has nothing to do with permissions.

    タイプ

    質問

    表示

    1.7K

    いいね!

    0

    返信

    0
  • Hi All, Recently we had VM migration from an old location to another one. The migration cloned one branch of the whole architecture as the following: author -> publisher -> dispatcher. Nothing changes except the new clone has a new domain name. Now we found a problem, the dispatcher doesn't cache. W...

    タイプ

    質問

    表示

    1.8K

    いいね!

    0

    返信

    6
  • Thanks for your advice, it's really helpful. I am actually doing mostly as you are advising. It's impossible to copy and paste as I am looking deeper into the two different versions.

    タイプ

    質問

    表示

    2.9K

    いいね!

    0

    返信

    0
  • Do we have to follow Adobe's Archtype13 structure, or just keep the old if considering the easy way at the first step? Moving to new structure invites a lot of challenges such as package names, dependencies. But I am afraid keeping the old structure will not be compatible with 6.5.

    タイプ

    質問

    表示

    3.1K

    いいね!

    0

    返信

    0
  • Thank you! Yes, we are considering moving to CoralUI. Another challenge is we need to change all jsp, jstl to htl also.

    タイプ

    質問

    表示

    3.3K

    いいね!

    0

    返信

    0
  • Thanks for your advice, it's really helpful

    タイプ

    質問

    表示

    3.1K

    いいね!

    0

    返信

    0
  • Hi all, Wish everyone to stay well during this difficult time.We are considering to upgrade from 6.0 with sp3 to 6.5. I read through this article and it doesn't look like we need to run the repo conversion jar. The most difficult thing is the code migration. The structure is very different and it se...

    タイプ

    質問

    表示

    3.4K

    いいね!

    0

    返信

    8
  • Hi All,We are considering upgrading AEM 6.0 to AEM 6.3. With quite limited knowledge on this, can anyone suggest what would be the best solution for us?The following is what we have now:AEM 6.0 with SP1, SP2 and SP3Java 8 (1.8.0_201-b09)CRX: Apache Jackrabbit Oak 1.0.22Classis UIFrontend: Extjs, JSP...

    タイプ

    質問

    表示

    1.2K

    いいね!

    0

    返信

    1