spring-webflow.dtd

spring的WEB开发插件,支持多状态WEB开发

<?xml version="1.0" encoding="UTF-8"?>

<!--
	Spring Web Flow DTD
	Authors: Erwin Vervaet, Keith Donald
	
	This DTD defines the web flow XML syntax. Web flows capture the page flow
	in (part of) a web application.

	XML documents that conform to this DTD should declare the following doctype:

	<!DOCTYPE webflow PUBLIC "-//SPRING//DTD WEBFLOW//EN"
		"http://www.springframework.org/dtd/spring-webflow.dtd">
-->

<!--
	Defines the root element for a web flow definition. Web flows
	are composed of one or more states.
-->
<!ELEMENT webflow ( property*, ( action-state | view-state | decision-state | subflow-state | end-state )+ )>

<!--
	Unique identifier of the web flow; should be unique to all other web flows.
-->
<!ATTLIST webflow id ID #REQUIRED>

<!--
	Identifies the start state of the flow: the state where flow
	execution will begin.
-->
<!ATTLIST webflow start-state IDREF #REQUIRED>

<!--
	Identifier of the flow implementation exported in the configured registry, typically
	the Spring Bean Factory. This is similar to the <ref bean="myBean"/> notation of
	the Spring beans DTD.
-->
<!ATTLIST webflow bean CDATA #IMPLIED>

<!--
	Fully qualified implementation class of the flow exported in the configured registry.
	For this "by type" flow lookup to work, there must be exactly one Flow implementation
	exported of that type.
-->
<!ATTLIST webflow classref CDATA #IMPLIED>

<!--
	Fully qualified class of the flow implementation. An instance of the
	class will be instantiated and possibly autowired depending on the value of the
	autowire attribute.
-->
<!ATTLIST webflow class CDATA #IMPLIED>
	
<!--
	Dependency (aka collaborator) autowiring options for use when instantiating the flow 
	implementation with the class attribute.
-->
<!ATTLIST webflow autowire (no | byName | byType | constructor | autodetect | default) "default">

<!--
	Defines an action state: a state where an action is executed.
	Transitions triggered by the action(s) lead on to other states.
-->
<!ELEMENT action-state ( property*, entry?, action+, transition+, exit? )>

<!--
	Unique identifier of an action state; must be unique to this flow.
-->
<!ATTLIST action-state id ID #REQUIRED>

<!--
	Identifier of the action state implementation exported in the configured registry, typically
	the Spring Bean Factory. This is similar to the <ref bean="myBean"/> notation of
	the Spring beans DTD.
-->
<!ATTLIST action-state bean CDATA #IMPLIED>

<!--
	Fully qualified implementation class of the action state exported in the configured registry.
	For this "by type" flow lookup to work, there must be exactly one ActionState implementation
	exported of that type.
-->
<!ATTLIST action-state classref CDATA #IMPLIED>

<!--
	Fully qualified class of the action state implementation. An instance of the
	class will be instantiated and possibly autowired depending on the value of the
	autowire attribute.
-->
<!ATTLIST action-state class CDATA #IMPLIED>
	
<!--
	Dependency (aka collaborator) autowiring options for use when instantiating the action state 
	implementation with the class attribute.
-->
<!ATTLIST action-state autowire (no | byName | byType | constructor | autodetect | default) "default">

<!--
	Defines a single action to be executed.
-->
<!ELEMENT action ( property* )>

<!--
	Identifier of the action implementation exported in the configured registry, typically
	the Spring Bean Factory. This is similar to the <ref bean="myBean"/> notation of
	the Spring beans DTD.
-->
<!ATTLIST action bean CDATA #IMPLIED>

<!--
	Fully qualified implementation class of the action exported in the configured registry.
	For this "by type" action lookup to work, there must be exactly one Action implementation
	exported of that type.
-->
<!ATTLIST action classref CDATA #IMPLIED>

<!--
	Fully qualified class of the action implementation. An instance of the
	class will be instantiated and possibly autowired depending on the value of the
	autowire attribute.
-->
<!ATTLIST action class CDATA #IMPLIED>
	
<!--
	Dependency (aka collaborator) autowiring options for use when instantiating the action 
	implementation with the class attribute.
-->
<!ATTLIST action autowire (no | byName | byType | constructor | autodetect | default) "default">

<!--
	Optional name qualifier for the action. When specified, the action will
	qualify execution result event identifiers by this name. An action with
	a name is often referred to as a "named action".
-->
<!ATTLIST action name CDATA #IMPLIED>

<!--
	Name of the target method to be invoked to execute this action. The method's signature must
	be of the form: 'public Event ${method}(RequestContext) throws Exception'
-->
<!ATTLIST action method CDATA #IMPLIED>

<!--
	A property associated with an another element (action, state, ...). Properties are simple
	strings or typed information that allow you to annotate the element.
	For example, the 'caption' property might serve a GUI tooltip or logging statement, and
	the 'validatorMethod' property might specify a target method to invoke on a form action's
	validator in a particular action state.
-->
<!ELEMENT property ( value? )>

<!--
	The name of the property.
-->
<!ATTLIST property name CDATA #REQUIRED>

<!--
	The target type of the property value; to facilitate from-string type conversion. This type
	string may be an alias (e.g 'int') or a fully-qualified class (e.g. 'java.lang.Integer').
-->
<!ATTLIST property type CDATA #IMPLIED>

<!--
	The value of the property; a short-cut alternative to an explicit child 'value' element.
-->
<!ATTLIST property value CDATA #IMPLIED>

<!--
	The value of the property.
-->
<!ELEMENT value ( #PCDATA )>

<!--
	Defines a transition from one state to another. Transitions define the supported 
	paths through the flow.
-->
<!ELEMENT transition ( property*, action* )>

<!--
	The criteria that triggers this transition, typically taking into account the
	last event that occured in this flow. The exact interpretation of the attribute value depends
	on the TextToTransitionCriteria converter that is installed. The most basic value is a 
	static event id (e.g on="success"). Sophisticated, custom transitional expressions are also
	supported (e.g on="${#result == 'submit' && flowScope.attribute == 'foo'}, or
	on="class:example.web.MyCustomTransitionCriteria").
-->
<!ATTLIST transition on CDATA #REQUIRED>

<!--
	Target state of the transition.
-->
<!ATTLIST transition to IDREF #REQUIRED>

<!--
	Identifier of the transition implementation exported in the configured registry, typically
	the Spring Bean Factory. This is similar to the <ref bean="myBean"/> notation of
	the Spring beans DTD.
-->
<!ATTLIST transition bean CDATA #IMPLIED>

<!--
	Fully qualified implementation class of the transition exported in the configured registry.
	For this "by type" action lookup to work, there must be exactly one Transition implementation
	exported of that type.
-->
<!ATTLIST transition classref CDATA #IMPLIED>

<!--
	Fully qualified class of the transition implementation. An instance of the
	class will be instantiated and possibly autowired depending on the value of the
	autowire attribute.
-->
<!ATTLIST transition class CDATA #IMPLIED>
	
<!--
	Dependency (aka collaborator) autowiring options for use when instantiating the transition 
	implementation with the class attribute.
-->
<!ATTLIST transition autowire (no | byName | byType | constructor | autodetect | default) "default">

<!--
	Defines a view state: a state where a view will be rendered and control will be 
	returned to the user.
	Transitions triggered by user input from the view lead on to other states.
-->
<!ELEMENT view-state ( property*, entry?, transition+, exit? )>

<!--
	Unique identifier of a view state; must be unique to this flow.
-->
<!ATTLIST view-state id ID #REQUIRED>

<!--
	The name of the view that is expected to render when this view state is entered.
	When no view name is provided, this view state will act as a marker view state. A marker
	view state does not request the rendering of a view, it only pauses the flow and returns control 
	the client. Use a marker end state when another object is expected to generate the response.
	
	While this value may be a static view name, it may also be qualified with a prefix to denote a
	specific (possibly custom) ViewDescriptorCreator strategy. The "class:" prefix allows you to 
	define a custom ViewDescriptorCreator implementation (e.g class:example.MyViewDescriptorCreator).
	The "redirect:" prefix triggers creation of a RedirectViewDescriptorCreator which will request a
	redirect to a specific URL (e.g. redirect:/home.htm). The exact semantics are defined by the 
	installed TextToViewDescriptorCreator.
-->
<!ATTLIST view-state view CDATA #IMPLIED>

<!--
	Identifier of the view state implementation exported in the configured registry, typically
	the Spring Bean Factory. This is similar to the <ref bean="myBean"/> notation of
	the Spring beans DTD.
-->
<!ATTLIST view-state bean CDATA #IMPLIED>

<!--
	Fully qualified implementation class of the view state exported in the configured registry.
	For this "by type" action lookup to work, there must be exactly one ViewState implementation
	exported of that type.
-->
<!ATTLIST view-state classref CDATA #IMPLIED>

<!--
	Fully qualified class of the view state implementation. An instance of the
	class will be instantiated and possibly autowired depending on the value of the
	autowire attribute.
-->
<!ATTLIST view-state class CDATA #IMPLIED>
	
<!--
	Dependency (aka collaborator) autowiring options for use when instantiating the view state 
	implementation with the class attribute.
-->
<!ATTLIST view-state autowire (no | byName | byType | constructor | autodetect | default) "default">

<!--
	Defines state entry logic to be executed.  This logic will always execute when this state is entered.
-->
<!ELEMENT entry ( action+ )>