Hi @markus_bulla_adobe thank a lot for your vision, in fact first of all
I will investigate their currently instances because in my view there is
an application issue and the behavior it's only a side effects.
Hi All, on high volume of activation tree replication agents stuck or
going in block with high consumptions of machine resources. This lead to
a restart of the AEM instances. To avoid this could be useful to enable
"Batch Mode" on the replication agents? Or as alternative upgrade the
architecture with a replication-tier (merely a publish instances)
between author and publish as follow: - one replication agents on author
(reduce replication event on author so author could not stuck)- disable
Hi @Mayank_Gandhi I follow this steps: 1. Create the components in a
standard way2. Docx4j last version 8.1.6 and I use the ReferenceImpl3.
Inserted Docx4j in a dedicated folder in the project /lib/dependencies4.
Update the build script of Ant5. Update the component.xml with all
dependencies (in particular the creation of Jar file section) The best
way I find is using the ReferenceImpl of Docx4j. If you need more steps
let me know.
Hi at all, how is the best practices?Use Case:- 2 project in AEM, every
project have his own code base (basically equal)- On deploy each code
base on AEM will overwrite the bundle of the other project How is
possible to deploy or merge the two code base for not overwrite the each
other project bundle? Thanks
Hi Mayank Gandhi, thanks I resolved the issue. I change version of
docx4j and I used the Reference Implementation rather then MOXy and the
component work well as I expected. Thanks for your insight and link.
Hi I'm trying to integrate docx4j inside a custom component. The
component works well but when I release the component on workbench
docx4j doesn't work as I except. There is any resource somewhere for
integrating docx4j in a Livecycle component?