When executing the Invoke Web Services object in Opalis Integration Server, one or more of the following errors are returned in the Error Summary Text published data:
Unable to generate a temporary class (result=1).
error CS0029: Cannot implicitly convert type 'Opalis.WebServices.DynamicProxy.CustomType' to 'Opalis.WebServices.DynamicProxy.CustomType'
error CS0030: Cannot implicitly convert type 'Opalis.WebServices.DynamicProxy.CustomType' to 'Opalis.WebServices.DynamicProxy.CustomType'
A known issue with WSDL.EXE included in the .NET Framework can cause a proxy class to be generated incorrectly if an array of complex type includes an element that is also an array of complex type for which only one element exists.
There is no resolution available at this time however there are three available workarounds:
- Generate the proxy class manually using WSDL.EXE and then modify the proxy class where the datatype has been inappropriately created as a two-dimensional array (e.g. 'CustomType') and correct it to be a single-dimensional array (e.g. 'CustomType').
- Modify the datatype in the desired WSDL so that a second, optional element is included in the definition. This can be done by adding an element such as '<xs:element minOccurs="0" name="dummyElement" nillable="true" type="xs:string"/>'.
- Modify the complex type in the desired WSDL so that the boundary attributes are part of the complex type rather than the element (i.e. move the "minOccurs" and "maxOccurs" attributes to the complex type and remove them from the element).
for other considerations.
Article ID: 2486643 - Last Review: February 7, 2011 - Revision: 3.0
- Opalis Integration Server