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
This WSDL is SOAP 1.1, and claims to be WS-I 1.0 compliant, but gowsdl can't seem to handle some of the objects that are nested complexTypes. The formatter fails because some types don't seem to be parsed correctly.
These are two general examples I have been running into:
// Constants with odd characters (spaces and hyphens)// generated codeconst (
DriveTrain_FrontWheelDriveDriveTrain="Front Wheel Drive"
)
// I believe should beconst (
DriveTrain_Front_Wheel_DriveDriveTrain="Front Wheel Drive"
)
// Constants with hyphens// generated codeconst(
SwitchChromeMediaGallery_Multi-ViewSwitchChromeMediaGallery="Multi-View"
)
// I believe should beconst(
SwitchChromeMediaGallery_Multi_ViewSwitchChromeMediaGallery="Multi-View"
)
// Structs with no objectstypeVersionInfostruct {
XMLName xml.Name`xml:"urn:description7a.services.chrome.com VersionInfo"`*BaseResponseData []*`xml:"data,omitempty"`//missing object type
}
This may be a limitation of the project that I'm just not aware of, but I figured I would raise an issue just in case.
The text was updated successfully, but these errors were encountered:
@beckler I'm still working on this, that WSDL uncovered a couple of issues with attributes. Also, the schema doesn't reuse complex types but instead it embeds them inside elements which is kind of wacky but still valid XSD.
@beckler what I'm planing to do is to unwrap the embedded complex types since they are not being re-used anywhere else, leaving their fields become part of the parent type. This causes some clashes with existing attributes in the parent type so I'll see what I can do to fix that too.
This WSDL is SOAP 1.1, and claims to be WS-I 1.0 compliant, but gowsdl can't seem to handle some of the objects that are nested complexTypes. The formatter fails because some types don't seem to be parsed correctly.
These are two general examples I have been running into:
This may be a limitation of the project that I'm just not aware of, but I figured I would raise an issue just in case.
The text was updated successfully, but these errors were encountered: