I'm using CDATA in a soaprequest, eg:
<soap:Body>
<cais:SendMessage>
<!--Optional:-->
<cais:message><![CDATA[
<msg:RetrieveHumanResourceWorkAssignmentSchedulesRequest xsi:schemaLocation="http://schema.bpost.be/services/resource/workforce/WMPOpe... WMPOperationalPlanningCNSMessages_v001.1.xsd"
xmlns:humanresource2="http://schema.bpost.be/entities/humanresource/humanresour...; xmlns:workassignment="http://schema.bpost.be/entities/humanresource/workassignm...;
xmlns:msg="http://schema.bpost.be/services/resource/workforce/WMPOpe...;
xmlns:typehumanresourcecommon="http://schema.bpost.be/types/humanresource/humanresourcec...;
xmlns:typehumanresourcesearchcriteria="http://schema.bpost.be/types/humanresource/humanresources...; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<typehumanresourcesearchcriteria:RetrieveHumanResourceWorkAssignmentSchedulesSearchCriteria>
<typehumanresourcesearchcriteria:HumanResourceIdList>
<humanresource2:HumanResourceId>501470</humanresource2:HumanResourceId>
</typehumanresourcesearchcriteria:HumanResourceIdList>
<typehumanresourcesearchcriteria:WorkAssignmentDateSearchCriteria>
<typehumanresourcecommon:from>2016-05-22</typehumanresourcecommon:from>
<typehumanresourcecommon:to>2016-05-28</typehumanresourcecommon:to>
</typehumanresourcesearchcriteria:WorkAssignmentDateSearchCriteria>
<typehumanresourcesearchcriteria:PublishStateSearchCriteria>
<workassignment:PublishState>PUBLISHED</workassignment:PublishState>
</typehumanresourcesearchcriteria:PublishStateSearchCriteria>
</typehumanresourcesearchcriteria:RetrieveHumanResourceWorkAssignmentSchedulesSearchCriteria>
</msg:RetrieveHumanResourceWorkAssignmentSchedulesRequest>
]]>
</cais:message>
<!--Optional:-->
<cais:commandName>AtHome</cais:commandName>
</cais:SendMessage>
</soap:Body>
When I run it, it turns into:
<soapenv:Body>
<SendMessage xmlns="http://www.ortec.com/CAIS">
<message><![CDATA[
<msg:RetrieveHumanResourceWorkAssignmentSchedulesRequest xsi:schemaLocation="http://schema.bpost.be/services/resource/workforce/WMPOpe... WMPOperationalPlanningCNSMessages_v001.1.xsd"
xmlns:humanresource2="http://schema.bpost.be/entities/humanresource/humanresour...; xmlns:workassignment="http://schema.bpost.be/entities/humanresource/workassignm...;
xmlns:msg="http://schema.bpost.be/services/resource/workforce/WMPOpe...;
xmlns:typehumanresourcecommon="http://schema.bpost.be/types/humanresource/humanresourcec...;
xmlns:typehumanresourcesearchcriteria="http://schema.bpost.be/types/humanresource/humanresources...; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<typehumanresourcesearchcriteria:RetrieveHumanResourceWorkAssignmentSchedulesSearchCriteria>
<typehumanresourcesearchcriteria:HumanResourceIdList>
<humanresource2:HumanResourceId>501470</humanresource2:HumanResourceId>
</typehumanresourcesearchcriteria:HumanResourceIdList>
<typehumanresourcesearchcriteria:WorkAssignmentDateSearchCriteria>
<typehumanresourcecommon:from>2016-05-22</typehumanresourcecommon:from>
<typehumanresourcecommon:to>2016-05-28</typehumanresourcecommon:to>
</typehumanresourcesearchcriteria:WorkAssignmentDateSearchCriteria>
<typehumanresourcesearchcriteria:PublishStateSearchCriteria>
<workassignment:PublishState>PUBLISHED</workassignment:PublishState>
</typehumanresourcesearchcriteria:PublishStateSearchCriteria>
</typehumanresourcesearchcriteria:RetrieveHumanResourceWorkAssignmentSchedulesSearchCriteria>
</msg:RetrieveHumanResourceWorkAssignmentSchedulesRequest>
]]></message>
<commandName></commandName>
</SendMessage>
</soapenv:Body>
How can I avoid that < turns into <
(in SoapUI, it just works fine...)
No answers