You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/08/12 20:04:37 UTC
DO NOT REPLY [Bug 22358] New: -
Service.getPort(URL, Class) loses WSDL metadata
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=22358>.
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=22358
Service.getPort(URL, Class) loses WSDL metadata
Summary: Service.getPort(URL, Class) loses WSDL metadata
Product: Axis
Version: current (nightly)
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Basic Architecture
AssignedTo: axis-dev@ws.apache.org
ReportedBy: apachebugs@perham.net
When a client calls Service.getPort(URL, Class), it actually calls
Service.getPort(URL, null, Class) where null is the Port name. Since portName
is null, it cannot associate the Call with the WSDL metadata needed to correctly
format the SOAP message. The message always reverts back to encoded formatting.
This patch changes getPort(URL, QName, Class) to check for a null portName. If
it is null, it pulls the first port out of the wsdlService and uses that as its
port.
Note that getPort(Class) does the same thing already. I think this was just an
oversight when the three parameter version was being developed.