All Downloads are FREE. Search and download functionalities are using the official Maven repository.

model-bpel.1.6.1.source-code.ws-bpel_executable.xsd Maven / Gradle / Ivy

The newest version!



	
	
		
			Schema for Executable Process for WS-BPEL 2.0
			OASIS Standard
			11th April, 2007
		
	
	
	
	
	
		
			
				This is the root element for a WS-BPEL 2.0 process.
			
		
	
	
		
			
				
					
					
					
					
					
					
					
					
					
				
				
				
				
				
				
				
			
		
	
	
	
		
			
				This type is extended by other component types to allow elements and attributes from
				other namespaces to be added at the modeled places.
			
		
		
			
			
		
		
	
	
	
	
		
			
		
		
		
	
	
	
		
			
				All standard WS-BPEL 2.0 activities in alphabetical order. Basic activities
				and structured activities.
				Addtional constraints:
				- rethrow activity can be used ONLY within a fault handler
				  (i.e. "catch" and "catchAll" element)
				- compensate or compensateScope activity can be used ONLY
				  within a fault handler, a compensation handler or a termination handler
			
		
		
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
				
			
		
	
	
	
	
		
			
				
				
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
				
				
				
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
					
				
				
				
				
				
			
		
	
	
	
		
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
				
			
		
	
	
	
		
			
				
			
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
		
			
				This element can contain all activities including the activities
				compensate, compensateScope and rethrow.
			
		
	
	
		
			
				
				
				
				
			
		
	
	
	
		
			
				This element can contain all activities including the activities
				compensate, compensateScope and rethrow.
			
		
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				XSD Authors: The child element onAlarm needs to be a Local Element Declaration, 
				because there is another onAlarm element defined for the pick activity.
			
		
		
			
				
					
					
				
			
		
	
	
	
	
		
			
				
					
				
				
				
			
		
	
	
	
		
			
				XSD Authors: The child element correlations needs to be a Local Element Declaration, 
				because there is another correlations element defined for the invoke activity.
			
		
		
			
				
					
					
				
				
				
				
				
				
			
		
	
	
	
		
			
				XSD Authors: The child element correlation needs to be a Local Element Declaration, 
				because there is another correlation element defined for the invoke activity.
			
		
		
			
				
					
				
			
		
	
	
	
		
			
				
				
			
		
	
	
	
		
			
			
			
		
	
	
	
		
			
				
					
						
							
							
						
						
					
					
				
			
		
	
	
	
		
			
			
		
	
	
	
	
	
	
	
	
	
		
			
				
					
					
				
				
				
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
	
	
	
		
			
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
					
				
				
			
		
	
	
	
	
	
	
		
			
				
					
						
						
					
				
				
			
		
	
	
	
	
		
			
				
					
					
				
				
				
			
		
	
	
	
	
		
			
			
			
				
				
			
		
		
		
		
		
		
		
		
	
	
	
	
		
			
		
	
	
	
	
		
			
		
		
		
	
	
	
		
			
			
		
	
	
	
	
		
			
			
			
		
		
		
		
		
		
		
	
	
	
	
		
			
		
	
	
	
	
		
			
		
	
	
	
	
		
			
				
			
		
	
	
	
	
		
			
		
	
	
	
	
		
			
		
	
	
	
	
		
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
			
		
	
	
	
	
		
			
				
					
					
					
					
				
				
				
			
		
	
	
	
	
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
			
		
	
	
	
	
		
			
				
					
					
					
					
				
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
	
	
	
		
			
				XSD Authors: The child element correlations needs to be a Local Element Declaration, 
				because there is another correlations element defined for the non-invoke activities.
			
		
		
			
				
					
					
					
					
					
					
				
				
				
				
				
				
			
		
	
	
	
		
			
				XSD Authors: The child element correlation needs to be a Local Element Declaration, 
				because there is another correlation element defined for the non-invoke activities.
			
		
		
			
				
					
				
			
		
	
	
	
		
			
				
			
		
	
	
	
		
			
			
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
				
			
		
	
	
	
	
		
			
				XSD Authors: The child element onAlarm needs to be a Local Element Declaration, 
				because there is another onAlarm element defined for event handlers.
			
		
		
			
				
					
					
				
				
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
		
			
				
					
					
				
			
		
	
	
	
	
		
			
				XSD Authors: The child element correlations needs to be a Local Element Declaration, 
				because there is another correlations element defined for the invoke activity.
			
		
		
			
				
					
					
				
				
				
				
				
				
				
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
	
		
			
				XSD Authors: The child element correlations needs to be a Local Element Declaration, 
				because there is another correlations element defined for the invoke activity.
			
		
		
			
				
					
					
				
				
				
				
				
				
				
			
		
	
	
	
	
		
			
		
	
	
	
	
		
			
				There is no schema-level default for "exitOnStandardFault"
				at "scope". Because, it will inherit default from enclosing scope
				or process.
			
		
		
			
				
					
					
					
					
					
					
					
					
					
				
				
				
			
		
	
	
	
		
			
				This element can contain all activities including the activities
				compensate and compensateScope.
			
		
	
	
	
		
			
				This element can contain all activities including the activities
				compensate and compensateScope.
			
		
	
	
	
	
		
			
				
					
				
			
		
	
	
	
	
		
			
				
				
			
		
	
	
	
	
		
			
				
			
		
	
	
	
		
			
				
			
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
	
		
			
				
					
					
				
			
		
	
	
	
		
			
		
		
		
	
	
	
		
			
		
	
	
	
	
		
			
		
	
	
	
		
			
		
	
	
	
		
			
		
	
	
	
		
			
			
		
	
	




© 2015 - 2025 Weber Informatics LLC | Privacy Policy