axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen D Burroughs" <>
Subject Re: [wsif] Bug 13038 - WSIF's dynamic port/operation creation confusion about message names
Date Fri, 27 Sep 2002 11:36:44 GMT


You misquoted me slightly :-)

Here's a slightly more detailed version of my proposed "wsif-only" fix:

Try to find the bindingOperation using the input/output names given. Then
if no match is found, try using null for the input/output names. If a match
is then found we know that only one operation exists in the binding with
the same name as the operation we're looking for (for more details see the method in wsdl4j). Now check
the input/output names of the "matched" bindingOperation object. If they
are null then we accept it as a match. If they are not null then we
consider it to be a different operation.

One downside to this is that you inspect/iterate over the binding
operations twice. It's also still up for debate as to whether specifying
input/output names in a port type operation and not specifying them in the
corresponding binding operation is valid. The spec suggests it isn't for
overloaded operations, which makes sense, but seems to allow any
combination of port type/binding, input/output names for non-overloaded


Owen Burroughs

|         |           Anthony          |
|         |           Elder/UK/IBM@IBMG|
|         |           B                |
|         |                            |
|         |           27/09/2002 11:58 |
|         |           Please respond to|
|         |           axis-dev         |
|         |                            |
  |       To:                                              
  |       cc:       "Jeff Greif" <>                     
  |       Subject:  [wsif] Bug 13038 - WSIF's dynamic port/operation creation confusion about
message names                                          |

There's a bugzilla bug raised for wsif,, to do with wsif
not correctly finding an operation.

The problem is because the 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 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?


Anthony Elder
Web Services Development
IBM UK Laboratories,  Hursley Park
(+44) 01962 818320, x248320, MP208.

View raw message