Here's some more background on the issue...
WebLogic defines their own ClassLoader to allow for deploying of WAR files, etc. The
inheritance hierarchy for this looks something like this:
+ java.lang.ClassLoader
+ java.security.SecureClassLoader
+ weblogic.utils.classloaders.GenericClassLoader
+ weblogic.utils.classloaders.ChangeAwareClassLoader
In order to locate META-INF/services/org.apache.axis.EngineConfigurationFactory, one
calls classLoader.getResources(...), which in turn uses the
findResources() method defined by java.lang.ClassLoader. The default implementation
of findResources is to return an empty Enumeration. None of the
classes in the above inheritance hierarchy provide an alternate implementation for
findResources. Thus, any JAR file which is loaded via the
ChangeAwareClassLoader will be ignored in the search for META-INF/services/...
Mind you, this is not the only defect I've found in WebLogic's class loading
implementations... :-/
Cheers,
--Doug
P.S. In the above inheritance hierarchy, the names of the classes may not be 100%
accurate... but you get the point.
-----Original Message-----
From: Richard Sitze [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 12:54 PM
To: [EMAIL PROTECTED]
Subject: [axis] VOTE: 13005: axis.EngineConfigFactory property not
working
I've corrected 13005, which enables the system property
axis.EngineConfigFactory override.
My +1 to put this in 1.0...
FYI, I can live without it, but there will be some users upset with me
(since I knocked it out in the first place) if it's not in 1.0. In
particular, 13005 documents that BEA's WebLogic has problems with the new
service mechanism (and I don't understand that).
<ras>
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
