DO NOT REPLY [Bug 27221] New: - Stubs ex WSDL2Java don't set port name

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27221>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27221

Stubs ex WSDL2Java don't set port name

           Summary: Stubs ex WSDL2Java don't set port name
           Product: Axis
           Version: 1.0
          Platform: PC
               URL: http://ws.microsoft.com/mscomservice/mscom.asmx?WSDL
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: gtr@ast.cam.ac.uk


If I generate Java from WSDL (see elsewhere in this ticker for the URL for the 
WSDL I'm testing with), the stubs do not set the portName attribute on the call 
object. This means that handlers set up with the techniques in JAX-RPC (as 
opposed to the non-standard shortcuts in Axis) aren't triggered by Call.invoke() 
since there is, apparently, one JAX-RPC handler-chain per port-name.

If the emitted stub called

  _call.setPortName(new QName(...));

in its constructor, then the pure-JAX-RPC handlers would work.

I realize that Axis has other ways of setting up handlers, but I'm trying to 
produce a client-side helper class that will work with any JAX-RPC 
implementation.