Perhaps this is a bug? I removed my custom wsdl and let Axis2 generate it for me. I am seeing the same issue while trying to get the class loader for the java.lang.Boolean class. I suspect since this class is in the boot class loader, null is returned from getClassloader() call? Can anyone suggest a workaround to force the Boolean class into the webapp class loader? If this IS a bug, should I log a JIRA, or is it a KI? Thanks, Ted
________________________________ From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 6:00 PM To: [email protected] Subject: RE: [Axis2] java.lang.IllegalArgumentException: null rcl More info... In debug, I can see the issue is spawning from the following call to the constructor of ReflectClassBuilder in the JamServiceFactoryImpl class (from the annogen jar): public ReflectClassBuilder(ClassLoader rcl) { if (rcl == null) throw new IllegalArgumentException("null rcl"); mLoader = rcl; } There is a class loader array with two values: a null and a system class loader. The null class loader is being passed in this case for a class of type java Boolean. The java object arrays seem to process fine prior to this point. Any ideas? I am using Axis2 1.1.1. Thanks, Ted ________________________________ From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 2:05 PM To: [email protected] Subject: [Axis2] java.lang.IllegalArgumentException: null rcl I am encountering the following exception in the Stax parser of Axis2 while rendering the results from my web service: org.apache.axiom.om.OMException: java.lang.IllegalArgumentException: null rcl I have read some threads indicating there issues related to java collections returned in Axis2. I have arrays of java objects being returned. Does anyone know if this is indeed an issue and if there is a workaround? Thanks, Ted
