Have you bundled any xslt jars with your application? You probably need to export the requisite WildFly modules to get this to work correctly. I would also recommend injecting a WildFly managed cache, rather than using using an Infinispan cache loaded from an infinispan xml file. The primary difference is that WIldFly configures Infinispan's marshaller to resolve classes using WildFly's modular class loader, whereas Infinispan's native configuration will rely on the TCCL.
Honestly, I have not yet tested Infinispan's distributed execution framework on WildFly - so there may likely be other classloading issues related to callable serialization that might prevent this from working. Let me know if you get stuck.
Paul, thanks for advice! Yes, I have bundled xalan jar with the application. When there is one server only, it works fine; and works fine with initiating server in the cluster, only remote server has error. I am still trying.
Sorry for one newbie question -- would WildFly managed cache provide load-balancing feature as Infinispan does? Do you have any link for me to start looking at? I thought WildFly always uses Infinispan under the hood.