Description of problem:
If JDG is used in embedded (library) mode and the application use JDG as modules the jgroups configuration files:
which might included in the application are shadowed, the customer configuration is overriden by the JDG default files.
The problem is that these filenames are used very often in examples so there is a high risk that they are used in real applications.
This behaviour is different if the infinispan libraries are included in the application packaging instead of the module dependency.
If the configuration file names jgroups-ec2.xml, jgroups-tcp.xml, jgroups-udp.xml are used in an application the cluster configuration does not have any effect as it will be overriden by the default files and this causes the use of wrong IP addresses or ports for cluster communication.
The files should provided in the customer context should never shadowed by files included in the infinispan library
The application should use individual application names for the jgroups configuration files to not have this issue.