Troubleshooting
Problem
When a property is defined as nillable but has a minimum occurrence of 1, you cannot set the property to null in a SOAP
Cause
Property with the nillable attribute and the minOccurs attribute defined as greater than 0. For illustrative purposes, the VirtualHostPort element.
<xsd:element name="VirtualHostPort" type="tns:dmIPPort" nillable="1" minOccurs="1" maxOccurs="1" />
Environment
SOAP <dp:set-config> requests with a property that uses the nillable attribute.
Diagnosing The Problem
When you attempt to define a configuration that contains elements with the nillable attribute and the minOccur attribute defined as 1, an error message is generated depending on the request.
- When the <dp:set-config> request does not contain the property entirely, you receive the following error when internal logging is enabled.
- When the <dp:set-config> request contains the an empty element, you receive the following error when internal logging is enabled.
Processing of '' stopped: https://host:5550/service/mgmt/3.0: cvc-particle 2.1: in element TargetBackendServersStandard of type {http://www.datapower.com/schemas/management}dmISAMReverseProxyBackendServersStandard, found
Processing of '' stopped: https://host:5550/service/mgmt/3.0: cvc-simple-type 1: element VirtualHostPort of type {http://www.datapower.com/schemas/management}dmIPPort may not be empty
Resolving The Problem
The schema for the SOAP request requires that the element be defined. You can define a null value with the xsi:nil attribute; for example: <VirtualHostPort xsi:nil="true"/>
When you use the xsi:nil attribute, you must define the xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" namespace in the XML content.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21689631