ec0da2601e
Bug fixed when firstName, surname or nif are null in a worker to be imported with the REST service. Now, Worker::checkConstraintUniqueFirstName checks if such fields are null.
30 lines
1.1 KiB
XML
30 lines
1.1 KiB
XML
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
|
|
|
|
<resource-list xmlns="http://rest.ws.navalplanner.org">
|
|
|
|
<!-- *** Machines *** -->
|
|
<!-- OK -->
|
|
<machine code="m1" name="m1-name" description="m1-desc"/>
|
|
<!-- Missing code and name (description is optional). -->
|
|
<machine code="" description=""/>
|
|
|
|
<!-- *** Workers *** -->
|
|
<!-- OK -->
|
|
<worker first-name="w1-firstName" surname="w1-surname" nif="w1-nif">
|
|
<criterion-satisfaction-list>
|
|
<criterion-satisfaction
|
|
criterion-type-name="WORK_RELATIONSHIP"
|
|
criterion-name="hiredResourceWorkingRelationship"
|
|
start-date="2009-01-01"
|
|
finish-date=""/>
|
|
<criterion-satisfaction
|
|
criterion-type-name="LEAVE"
|
|
criterion-name="paternityLeave"
|
|
start-date="2009-12-24"
|
|
finish-date="2009-12-25"/>
|
|
</criterion-satisfaction-list>
|
|
</worker>
|
|
<!-- Missing first name, surname, and nif. -->
|
|
<worker first-name="" nif=""/>
|
|
|
|
</resource-list>
|