serviceref_2_0.xsd

jbpm-bpel-1.1.Beta3 JBoss jBPM Starters Kit 是一个综合包

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://schemas.xmlsoap.org/ws/2004/03/business-process/service-ref"
			xmlns:sref="http://schemas.xmlsoap.org/ws/2004/03/business-process/service-ref"
			xmlns:xsd="http://www.w3.org/2001/XMLSchema"
			elementFormDefault="qualified">
	
	<!-- SCHEMA TODO: the namespace of this schema needs to be finalized -->
	
	<xsd:annotation>
		<xsd:documentation>
			2006-07-28: Rev 1.1: YIU-OSS: Alex Yiu:
				Apply Issue a portion of Issue 294.1:
				Create a schema of a separate namespace for "service-ref"
			2006-08-07: Rev 1.2: Thomas Schulze
				Minor formatting changes. Reviewed the comments.
				Removed the default namespace.
				Changed prefix "serviceref:" to "sref:".
		</xsd:documentation>
	</xsd:annotation>
	
	<xsd:element name="service-ref" type="sref:ServiceRefType">
		<xsd:annotation>
			<xsd:documentation>
				This element can be used within a from-spec.
			</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="ServiceRefType">
		<xsd:annotation>
			<xsd:documentation>
				This type definition is for service reference container.
				This container is used as envelope to wrap around the actual endpoint reference value,
				when a BPEL process interacts the endpoint reference of a partnerLink.
				It provides pluggability of different versions of service referencing schemes
				being used within a BPEL program. The design pattern here is similar to those of
				expression language.
			</xsd:documentation>
		</xsd:annotation>
		<xsd:sequence>
			<xsd:any namespace="##other" processContents="lax"/>
		</xsd:sequence>
		<xsd:attribute name="reference-scheme" type="xsd:anyURI"/>
	</xsd:complexType>
	
</xsd:schema>