When using WebLogic classpath extensions to place a jar containing a Gaderian descriptor on the classpath, WebLogic will expose this jar as two, identical, class path entries.
These two entries will be processed by Gaderian and cause an error since they both have the same module ids etc.
Changing the XmlModuleDescriptorProvider to load all resources into a set instead of a list before beginning processing will fix this issue
This is of course incorrect behaviour from WebLogic but alas.
Changed to use a set for initial collection of resources