This is something that I've also noticed. I sent a mail to the Adobe Credential Team to inquire about that.

I'm trying to install and configure the S3 connector for the AEM datastore using the directions provided in the Adobe documentation on this page: https://docs.adobe.com/docs/en/aem/6-1/deploy/platform/data-store-config.htmlHowever, I'm having no luck getting it to work. I am using a bare AEM 6.1 ins...

Using the Touch UI the feature of Image cropping only supported using the inline editor. It's not supported on Touch dialogs.Alternatively the user could crop the image directly from the DAM. That should have the same effect.

Try doing a bit of reading & learning: http://www.amazon.com/Beginning-Java-EE-Expert-Voice/dp/143024626X

I would also go with the option of setting up a separate Tomcat.Getting Apache CXF to work as SOAP service within the OSGi runtime of AEM will be very complex, if not impossible due to dependency conflicts.Take a look at Apache Mule, the concept is interesting!

Thanks for the additional article. I now have a clear picture of how the mmap mechanism works!

I stumbled upon a blogpost where Jorg Hoh claims that putting your TarMK on an NFS is not a good idea because mmap (Java 1.7) won't work with that configuration.Short summary: Having TarMK storage on an NFS causes a huge performance impact as AEM won't be able to take advantage of memory mapped file...