There's a bugzilla bug raised for wsif, http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13038, to do with wsif not correctly finding an operation.
The problem is because the wsdl, http://www.ebi.ac.uk/xembl/XEMBL.wsdl, specifies an input name on the operation in the portType, but does not specify a name on the input in the binding. This causes the wsdl4j method getBindingOperation in com.ibm.wsdl.BindingImpl to return null when wsif calls it with the operation, input, and output names from the portType. Reading the wsdl spec it not clear to me if it is valid wsdl to leave out the names on the binding when they're specified in the portType. If it is valid is this a wsdl4j bug or should wsif work around it? We could fix it in wsif by doing something like (thanks Owen) trying to find the bindingOperation using the input/output names given, then if no match is found try using null for the input/output names, and then if still no match is then found check to see if the binding input/output names for the matched operation are null. If they are then use that bindingOperation. If not then return null since it is not a "match". What does anyone think? ...ant Anthony Elder [EMAIL PROTECTED] Web Services Development IBM UK Laboratories, Hursley Park (+44) 01962 818320, x248320, MP208.
