Unfortunately, the issue in the mentioned JIRA is not completely resolved. In running the test case from the JIRA, the null class loader is fixed, but the set still cannot be deserialized. I went ahead and attached the BeanUtil class change with comments.
Thanks, Ted -----Original Message----- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 7:26 AM To: [email protected] Subject: RE: [Axis2] java.lang.IllegalArgumentException: null rcl Thanks for figuring it out Ted .. please attach as a patch to that JIRA! Thanks, Sanjiva. On Mon, 2007-02-12 at 14:30 -0600, Ted Jones wrote: > I was able to resolve this issue with a minor change to the > getPullParser(Object, QName, TypeTable, boolean) method of > org.apache.axis2.databinding.utils.BeanUtils. > > Changing: > > jam_service_parms.addClassLoader(beanObject.getClass().getClassLoader( > )); > > to: > > ClassLoader cl = beanObject.getClass().getClassLoader(); > if (cl!=null){ > jam_service_parms.addClassLoader(cl); > }else{ > > jam_service_parms.addClassLoader(Thread.currentThread().getContextClas > sLoader()); > } > > averted the null class loader and properly deserialized my java > Boolean. This seems like a solid resolution and may fix another > (seemingly related?) JIRA I came across: > https://issues.apache.org/jira/browse/AXIS2-2054?page=com.atlassian.ji > ra.plugin.system.issuetabpanels:all-tabpanel > > > > > ______________________________________________________________________ > From: Ted Jones [mailto:[EMAIL PROTECTED] > Sent: Monday, February 12, 2007 10:20 AM > To: [email protected] > Subject: RE: [Axis2] java.lang.IllegalArgumentException: null rcl > > > > 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 -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
