Done issues

Using classpath extensions in WebLogic causes identical URL resources to be loaded
GAD-32
Conditional rules should allow the currently running OS as a conditional expression
GAD-31
Descriptor documentation should be re-organised to follow the XML "flow"
GAD-26
Service proxies won't work with covariant return types
GAD-7
All service not using 3rd party libraries should be migrated to core
GAD-29
Builder Factory should allow for a flag to skip Required annotation checks
GAD-30
Symbol source error message should clearer when a symbol can not be expanded.
GAD-27
It should be possible to define the default service implementation factory for the whole module
GAD-25
JDK Proxy Factory
GAD-23
HiveMind can't inject a numeric value in an Integer property of a bean.
GAD-22
Core module contains META-INF/hivemodule.xml
GAD-21
BeanFactory should support beans with no-args constructor
GAD-20
ClassFactoryClassLoader conceals loader resources
GAD-19
HiveMind LoggingInterceptor does not log java.lang.Error
GAD-18
FileResource doesn't implement hashCode()
GAD-17
ShutdownCoordinator tries to construct unconstructed services.
GAD-16
registryDidShutdown() Called Twice on Bean Service
GAD-15
Registry.getServiceIds() doesn't support concrete class service points
GAD-14
No line precise error reporting on failed translate
GAD-13
NullPointerException if hivemodule is an empty file
GAD-12
Proxy creation failure for non-interface beans
GAD-11
Will not work in with security enforcments due to bug in Javassist
GAD-10
Service Serialization doesn't work on a cluster
GAD-9
Error message when more than 1 service is available - visible - for auto-wiring could be clearer
GAD-8
Poms should be updated to use the OPS4J root pom
GAD-5
translator attribute ignores default unless you also specify skip-if-null="false"
GAD-1
xdoc files does not conform to XSD (http://maven.apache.org/xsd/xdoc-2.0.xsd)
GAD-4
issue 1 of 27

Using classpath extensions in WebLogic causes identical URL resources to be loaded

Description

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.

Environment

None

Status

Assignee

JohanL

Reporter

JohanL

Labels

None

Components

Fix versions

Affects versions

1.0

Priority

Trivial