[wsf-dev] lu:Status

Cahill, Conor P conor.p.cahill at intel.com
Wed Dec 19 03:13:45 PST 2007


You are reading this correctly.   The reason is to support multi-event
status
reports for partial success.    So the prototypical example would be:

	<status code="Partial">
		<status code="NotFound" ref="abc" />
		<status code="Success" ref="def" />
		<status code="Success" ref="ghi" />
		<status code="PermissionDenied" ref="jkl" />
	</status>

The top level status is required to be Success or Failed (or Partial for

multi-item transactions).  The Second level status is optional.  For 
single item transactions it would contain one status indicating the more
detailed failure code.  For multi-item transactions it would be as shown
above, with a ref or positional link to the respective item in the
request.

Conor

> -----Original Message-----
> From: wsf-dev-bounces at lists.openliberty.org [mailto:wsf-dev-
> bounces at lists.openliberty.org] On Behalf Of Asa Hardcastle
> Sent: Tuesday, December 18, 2007 9:24 PM
> To: wsf-dev at lists.openliberty.org
> Subject: [wsf-dev] lu:Status
> 
> 
> In the idwsf utility v2.0 schema (urn:liberty:util:2006-08) the Status
> type appears to be defined so that it can have itself as a child
> element making this a completely legal XML fragment:
> 
> ...
> <Status code="Failed">
>    <Status code="MissingSecurityMechIDElement"/>
>    <Status code="MissingSelect"/>
> </Status>
> ...
> 
> and actually:
> 
> <Status code="Failed">
>    <Status code="MissingSecurityMechIDElement">
>      <Status code="NoFunWithoutSechMechId"/>
>      <Status code="BigTimeFailed">
>          <Status code="ForSure" comment="Totally for sure"/>
>      </Status>
>    </Status>
>    <Status code="MissingSelect"/>
> </Status>
> 
> 
> 
> Am I reading this XSD properly?
> 
> 
>      <xs:complexType name="StatusType">
>          <xs:annotation>
>              <xs:documentation>
>                  A type that may be used for status codes.
>              </xs:documentation>
>          </xs:annotation>
>          <xs:sequence>
>              <xs:element ref="Status" minOccurs="0"
> maxOccurs="unbounded"/>
>          </xs:sequence>
>          <xs:attribute name="code" type="xs:string" use="required"/>
>          <xs:attribute name="ref" type="IDReferenceType"
> use="optional"/>
>          <xs:attribute name="comment" type="xs:string"
use="optional"/>
>      </xs:complexType>
> 
>      <xs:element name="Status" type="StatusType">
>          <xs:annotation>
>              <xs:documentation>
>                  A standard Status type
>              </xs:documentation>
>          </xs:annotation>
>      </xs:element>
> 
> 
> If I'm reading this properly, why was this decision made?
> 
> 
> thanks in advance,
> 
> asa
> 
> 
> 
> --
> Asa Hardcastle, Technical Lead, openLiberty ID-WSF ClientLib
> Tel: +1.413.429.1044 Skype: subsystem7
> 
> 
> _______________________________________________
> Wsf-dev mailing list
> Wsf-dev at lists.openliberty.org
> http://lists.openliberty.org/mailman/listinfo/wsf-
> dev_lists.openliberty.org



More information about the Wsf-dev mailing list