Yes, this is one of the mitigations steps.

Please refer to the following tutorials for the same:https://experienceleague.adobe.com/docs/experience-manager-65/forms/getting-started/create-first-interactive-communication/create-your-first-interactive-communication.html?lang=en#step-create-form-data-model https://experienceleague.adobe.com/docs...

AEM ships with an EOL version of log4j (1.2.17) which is only impacted if the JMSAppender class is used. This is not the case for OOTB AEM.1. ls Adobe aware of this Apache log4J library vulnerability?Yes. Adobe is aware of this Apache tog4j library vulnerability.2. Does Adobe use the Apache log4J li...

Seems like this is not yet supported, as there is no mention of this in the public documentation.

I would suggest you to use Adaptive Forms(instead of HTML5 forms) using the same XDP template, , as adaptive forms offers Form data model, using which you can easily achieve this use case.

For HTML Forms, you can inject the data using data and dataRef attributes only, as explained here. 

There are missing properties in your XSD. Make sure your XSD follows the following sample XSD's structure: <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="Work" type="workType"/> <xsd:complexType name="workType"> <xsd:sequence> <xsd:element na...

Yes, it is expected to work in Development environment, but we would recommend to test this on an OS Server for the best results. Thank you!  

Sorry Mark, but even Windows 10 is also not supported, as per the link. You need to use 64 bit Windows Servers like the versions 2012 R2 or 2016, as per the link above. Windows 10 or Windows 11 are not Windows Servers. 

AEM Forms 6.4 JEE is not supported on Windows 11. For supported OS, please refer to this link. Thanks!