998 2003-06-13 09:55 Alpha 4 ReflectionUtils class problem 2004-05-28 15:48:14 1 1 1 Unclassified Java WS Core globus_ogsi_core alpha PC All RESOLVED FIXED P2 major --- 1 hansenb@us.ibm.com lane@mcs.anl.gov afhieter@us.ibm.com childers@mcs.anl.gov joecwell@us.ibm.com ogsa-bugs@globus.org sandholm@mcs.anl.gov hansenb@us.ibm.com 2003-06-13 09:55:15 I am working on a web based OGSA management UI, and have run into a problem using the ReflectionUtils class (package org.globus.ogsa.client.reflection) in Alpha 4 that I did not have in Alpha 3 or earlier. Specifically, I am calling the getOperationDescriptions method to obtain all of the operation information for a specific port type ... typical call being: portTypeOperationList = ReflectionUtils.getOperationDescriptions( gsr.getWSDLDefinition(), gsr.getDocument(), aPortType ); Starting in Alpha 4, the call now fails most of the time with a null pointer exception. But in some cases it does still work. It appears to only fail if the NamespaceURI of the QNAME representing the port type (ie. aPortType in the call above) is specifically a new value that started showing up in the toolkit services themselves after Alpha 3 ... the new value being: http://www.gridforum.org/namespaces/2003/03/OGSI The error is: java.lang.NullPointerException at org.globus.ogsa.client.reflection.ReflectionUtils.getOperationDescriptions (ReflectionUtils.java:113) I located a similar call to the ReflectionUtils.getOperationDescriptions method inside the toolkit service browser gui that it uses trying to create dynamic operation panels, and it also fails with the same error when I execute the toolkit service browser (under the same port type namespace URI conditions). Is anyone in toolkit development already aware of this condition in Alpha 4? If not, could you verify whether it is an actual problem or not? I think it may have been introduced in Alpha 3.5, but I went directly from Alpha 3 to Alpha 4, so I didn't see it until then. Thanks in advance. Cheers - Joe Caldwell <joecwell@us.ibm.com> (bugzilla entered by Bob Hansen) Note: we're seeing a similiar problem in the beta, but have not fully diagnosed it as of yet. lane@mcs.anl.gov 2003-06-18 18:46:22 Though this is actually an issue with certain wsdl schemas inheriting gwsdl schemas instead of being setup and processed with GWSDL2WSDL properly as per the guide and samples, this modification returns operation information for the dervied port type of which the wsdl schema exists for as opposed to the port type that is actually being requested.