You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2019. It is now read-only.
When a JAX-WS compliant tool generates the client-side proxy codes from a WSDL,
some of the WSDL to JAVA mapping metadata are preserved in the annotations. We
have found however the metadata in the annotations are insufficient for the
proxy to be fully functional in the runtime. When a proxy/generatedService
instance is initialized in the runtime, it must read the WSDL before it can
process the first request. Requiring the WSDL in the proxy initialization has
become a problem on the implementation.
Following is a list of the metadata that should have been maintained in the
annotation:
SOAP Version
Endpoint Address
Attachment/MIME part binding
RPC style body namespace
wsdl:message/wsdl:part@name
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered:
[email protected] said:
RequestWrapper.partName and ResponseWrapper.partName have been added since 2.2
MR3. The partName of a fault message is still not preserved in annotation.
Proposal: add WebFault.partName.
When a JAX-WS compliant tool generates the client-side proxy codes from a WSDL,
some of the WSDL to JAVA mapping metadata are preserved in the annotations. We
have found however the metadata in the annotations are insufficient for the
proxy to be fully functional in the runtime. When a proxy/generatedService
instance is initialized in the runtime, it must read the WSDL before it can
process the first request. Requiring the WSDL in the proxy initialization has
become a problem on the implementation.
Following is a list of the metadata that should have been maintained in the
annotation:
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered: