| Summary: | Destroy doesn't adhere to WS-Lifetime schema | ||
|---|---|---|---|
| Product: | gRAVI | Reporter: | Josh <JRBoverhof@lbl.gov> |
| Component: | gRAVI | Assignee: | Josh <JRBoverhof@lbl.gov> |
| Status: | NEW | ||
| Severity: | normal | CC: | madduri@mcs.anl.gov |
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
sample client does this: resClient.destroy(null); soap like this: <soapenv:Body> <Destroy xsi:nil="true" xmlns="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd"/> </soapenv:Body> Here is the schema for ws-lifetime: <xsd:element name="Destroy"> <xsd:complexType/> </xsd:element> By default elements ARE NOT nillable. Thus the instance is illegal, this should be caught in the ws-layer.