----- Original Message ----- From: "Jens Schumann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 27, 2003 09:50 Subject: Resource Access
> I have been thinking a bit about Steve's comments on getting the class and > resource loading straight, and I agree, there is testing required before > looking at a fix. > > While dealing with the Orion Server issue I came to the conclusion that the > only way to get it right is to build up some kind of test suite and run it > on different app servers. A JSP page that you drop in anywhere and generates an XML report is a good way to do this...I could even imagine it becomes part of the happyaxis config probing over time. >The actual test should return the classloader > hierarchy for several important classes/resources: > > > server-config.wsdd > AxisServlet.java > AxisServer.java > WSDDProvider.java > > A custom Provider. > A custom Handler. > A custom AxisServlet. > All WebService Stubs/Skeletons and and least one complex type class (a value > object, for instance). > > More TBD. > -dump info about the various class and resource loaders (context, servlet.loadResource()); see if the war is expanded, etc, etc.
