Resolution:
In FabricServer, when using an EAR archive in a Domain with JBoss as a container on a Windows Engine, a ClassNotFoundException occurs. The same EAR archive works on a standalone JBoss server outside of FabricServer.

This problem occurs on the Windows OS when the total pathname for the EAR is longer than the Windows 256-character filename limit. The JBoss path is constructed as follows:

C:\Program Files\DataSynapse\Engine\work\[ENGINE HOSTNAME]-[INSTANCE #]\server\ds_node[INSTANCE #]\tmp\deploy\tmp[5-DIGIT ID][EAR FILE NAME].ear-contents\[WAR FILE NAME]-exp.war\WEB-INF\[SUBDIRECTORIES AND FILES]

For example, for an EAR file jbgs.ear that contains a WAR testharness_jbossgenericserviceWAR.war:

C:\Program Files\DataSynapse\\Engine\work\qapc54-1\server\ds_node1\tmp\deploy\tmp55883jbgs.ear-contents\testharness_jbossgenericserviceWAR-exp.war\WEB-INF\classes\com\datasynapse\fabric\testharness\engine\servletEJBGenericServiceServlet.class

To avoid this issue , you could rename your EAR or WAR archive to a shorter filename, change the paths in the WAR archive, or change the installation location of your Engines to a shorter path.

JBoss ClassNotFoundException when using EAR archive