[jbosstools-commits] JBoss Tools SVN: r2569 - trunk/shale/plugins/org.jboss.tools.shale/resources/meta.

Author: scabanovich Date: 2007-07-20 13:21:10 -0400 (Fri, 20 Jul 2007) New Revision: 2569 Removed: trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-clay-config_1_0.dtd trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-dialog-config_1_0.dtd trunk/shale/plugins/org.jboss.tools.shale/resources/meta/spring-beans.dtd Log: EXIN-86 Third party dtds and schemas removed Deleted: trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-clay-config_1_0.dtd =================================================================== --- trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-clay-config_1_0.dtd 2007-07-20 17:19:09 UTC (rev 2568) +++ trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-clay-config_1_0.dtd 2007-07-20 17:21:10 UTC (rev 2569) @@ -1,283 +0,0 @@ -<?xml version='1.0' encoding="UTF-8"?> - - -<!-- - - Copyright 2004-2005 The Apache Software Foundation. - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - - $Id: shale-clay-config_1_0.dtd,v 1.1 2005/12/23 14:01:34 glory Exp $ - ---> - -<!-- - - DTD for view definitions used by the "org.apache.shale.clay" package. - To support validation of your configuration file, include the following - DOCTYPE element at the beginning (after the "xml" declaration): - - <!DOCTYPE view PUBLIC - "-//Apache Software Foundation//DTD Shale Clay View Configuration 1.0//EN" - "http://struts.apache.org/dtds/shale-clay-config_1_0.dtd"> - ---> - -<!-- - The BindingType enumeration defines how Expression Language (EL) binding is - handled. - VB - Use Value Binding - MB - Use Method Binding - None - No use of EL. The value passes through - Early - EL evaluated before setting the component property/attribute. ---> -<!ENTITY % BindingType "(VB|MB|None|Early)"> - - -<!--Boolean enumeration as two values that correspond to a boolean primitive data type--> -<!ENTITY % Boolean "(true|false)"> - -<!-- - The "attributes" node contains all of the attributes that will be applied to the - the target "component" or "element". Individual attributes are specified using the - "set" node, a child element. - - When using JSF/JSP tags to define composition, the attributes are specified in the body - of the begining JSP tag. In clay, all components are represented generically by a top-level - "component" or nested "element" node. The attributes are declared using the - "attributes" node verses a unique tag for each specific type of component. ---> -<!ELEMENT attributes (set+)> - -<!-- -The "symbols" node contains tokens that are replaced within meta-data attribute values. -The symbol token identifier is the at, '@', character. The scope of the symbols is the -"component" or "element" they are applied to. This includes all aggregated definitions. -This means that symbols can also inherited from an outer scope. The bindingType -attribute in the "set" node is ignored for the symbols collection. ---> - -<!ELEMENT symbols (set+)> - -<!-- - The "set" node represents an individual meta attribute that should be applied to the "component" - or "element" nodes. - - name - The attribute name that corresponds to a component property. The parent "attributes" node - container can be inherited. The "name" attribute acts as the "method signature" when - resolving inheritance. - - bindingType - This attribute is of BindingType. It indicates the contract that a component - property/attribute has with the proper use of EL. This attribute is only valid within - the attributes collection. - - value - This attribute holds the value of the named attribute. A literal string value or a dynamic bound - expression. ---> -<!ELEMENT set EMPTY> -<!ATTLIST set - name CDATA #REQUIRED - bindingType %BindingType; #IMPLIED - value CDATA #IMPLIED -> - -<!-- - A "component" represents a single top-level simple component or a subtree of components. - - attributes - A container to hold attributes that will be applied to the target component. - - symbols - A container to hold tokens that are replaced within attribute values. - - converter - A component can have a single converter which is the same relationship that - a JSF component would have to a Converter. JSF has a assumed rule that only components - implementing the ValueHolder interfaces can be assigned converters. This rule is enforced - at runtime and not through this document type definition. - - validator - A component can have zero or many associated validators. Only components that - implement the EditableValueHolder interfaces can be assigned validators. This rule - is enforced at runtime and not through this document type definition. - - actionListener - A component can have zero or many assigned actionListeners. Action listeners - can only be assigned to components implementing the ActionSource interfaces. This rule is - enforced at runtime. - - valueChangeListener - A component can have zero or many assigned valueChangeListeners. Change listeners - can only be assigned to components implementing the EditableValueHolder interfaces. This rule is - enforced at runtime. - - - element - A top-level "component" can contain any number of sub "elements". Elements define - composition for a complex component. The element is the glue that pulls in a "top-level" - component. The element is kind of like an inner class in that it can extend the attributes - of the "top-level" component that it's aggregating. - - - jsfid - A unique identifier defining the component instances as it relates to the - componentType. This is a required attribute. - - extends - A jsfid that this component will inherit characteristics from. A jsfid that this - component will inherit characteristics from. By characteristics we mean parent "elements" - and "attributes". This is an optional attribute. - - componentType - The component type will be the JSF registered logical name for Components, - Validators and Converters in the faces-config.xml file. For ActionListeners and - ValueChangeListeners, the component type will be the fully qualified class name. The - componentType will be required when the extends attribute is not specified. If the - extends attribute is specified it will inherit the attribute value from the parent - component. It can also override a extended component's type morphing it into - another type of component. - - allowBody - This attribute only applies when using the Clay template features and it - is optional. A "true" value is returned if the HTML child nodes under the node that - this meta component is bound to should be rendered; otherwise, a "false" value is - returned indicating the child nodes should be ignored. This feature allows you to - override design-time mockup HTML at runtime. - - facetName - Use this attribute to register the component in the facets collection rather - than the children collection. - ---> -<!ELEMENT component (attributes?, symbols?, converter?, validator*, actionListener*, valueChangeListener*, element*)> -<!ATTLIST component jsfid CDATA #REQUIRED - extends CDATA #IMPLIED - componentType CDATA #IMPLIED - id CDATA #IMPLIED - allowBody %Boolean; #IMPLIED - facetName CDATA #IMPLIED -> - -<!-- - The element nodes are the composition glue. The jsfid represents the top-level component that - the nested component will extend. The jsfid is used in the element like the componentType is - to the "component". The renderId is the unique namespace within the owning "component" or "element". - The key difference between an element and component is that a component can be reused within - any number of compositions where an element is the structure for defining the composition. - - attributes - A container to hold attributes that will be applied to the target component. These - attributes will override and extend attributes in the top-level component which is specified - by the "jsfid" attribute. - - symbols - A container to hold tokens that are replaced within attribute values. - - converter - A component can have a single converter which is the same relationship that - a JSF component would have to a Converter. JSF has a assumed rule that only components - implementing the ValueHolder interfaces can be assigned converters. This rule is enforced - at runtime and not through this document type definition. - - validator - A component can have zero or many associated validators. Only components that - implement the EditableValueHolder interfaces can be assigned validators. This rule - is enforced at runtime and not through this document type definition. - - actionListener - A component can have zero or many assigned actionListeners. Action listeners - can only be assigned to components implementing the ActionSource interfaces. This rule is - enforced at runtime. - - valueChangeListener - A component can have zero or many assigned valueChangeListeners. Change listeners - can only be assigned to components implementing the EditableValueHolder interfaces. This rule is - enforced at runtime. - - element - A "element" can contain any number of sub-elements. Elements define - composition for a complex component. The element is the glue that pulls in a "top-level" - component. The element is kind of like an inner class in that it can extend the attributes - of the "top-level" component that it's aggregating. - - renderId - A numeric integer value that uniquely defines the element within a owning "component" - or "element". It's the "method signature" used to resolve inheritances and also ordering - within the parent. A component that extends another can override or add nested "element"s - by renderId. - - id - This attribute corresponds to a JSF component's id attribute that will be used to derive - the client id value within the HTML id attribute. - - facetName - Use this attribute to register the component in the facets collection rather - than the children collection. - - componentType - The component type will be the JSF registered logical name for Components, - Validators and Converters in the faces-config.xml file. For ActionListeners and - ValueChangeListeners, the component type will be the fully qualified class name. The - componentType will be required when the extends attribute is not specified. If the - extends attribute is specified it will inherit the attribute value from the parent - component. It can also override a extended component's type morphing it into - another type of component. - ---> -<!ELEMENT element (attributes?, symbols?, converter?, validator*, actionListener*, valueChangeListener*, element*)> -<!ATTLIST element - renderId CDATA #REQUIRED - jsfid CDATA #REQUIRED - id CDATA #IMPLIED - facetName CDATA #IMPLIED - componentType CDATA #IMPLIED -> - -<!-- - A "converter" node is the meta component definition for a JSF converter. This - node can exist under a "component" or "element" node. A converter can only be - assigned to a JSF component implementing the ValueHolder interfaces. - - jsfid - The top-level component that defines a converter. The componentType - attribute of this component will should be a converter-id registered in - the faces-config.xml file. ---> -<!ELEMENT converter (attributes?)> -<!ATTLIST converter jsfid CDATA #REQUIRED> - -<!-- - A "actionListener" node is the meta component definition for a JSF action listener. This - node can exist under a "component" or "element" node. A action listener can only be - assigned to a JSF component implementing the ActionSource interfaces. - - jsfid - The top-level component that defines a converter. The componentType - attribute of this component will should be a fully qualified class name - of the java class implementing the ActionListener interfaces. ---> -<!ELEMENT actionListener (attributes?)> -<!ATTLIST actionListener jsfid CDATA #REQUIRED> - -<!-- - A "validator" node is the meta component definition for a JSF validator. This - node can exist under a "component" or "element" node. A converter can only be - assigned to a JSF component implementing the EditableValueHolder interfaces. - - jsfid - The top-level component that defines a validator. The componentType - attribute of this component will should be a validator-id registered in - the faces-config.xml file. ---> -<!ELEMENT validator (attributes?)> -<!ATTLIST validator jsfid CDATA #REQUIRED> - -<!-- - A "valueChangeListener" node is the meta component definition for a JSF value change listener. - This node can exist under a "component" or "element" node. A value change listener can only be - assigned to a JSF component implementing the EditableValueHolder interfaces. - - jsfid - The top-level component that defines a value change listener. The componentType - attribute of this component will should be a fully qualified class name - of the java class implementing the ValueChangeListener interfaces. ---> -<!ELEMENT valueChangeListener (attributes?)> -<!ATTLIST valueChangeListener jsfid CDATA #REQUIRED> - -<!-- - The "view" node is the root of the document. This document holds meta data used to - construct a sub component tree. It's a stand-in for the JSF JSP tags meaning that - the same information can be represented here using a very generic structure. - - component - A top-level meta component definition that can be reused across pages - and subtree compositions. - - A component can be directly included from within a clay component by it's unique - jsfid or tied to the view composition indirectly by a HTML template where the HTML - element has a binding jsfid attribute. ---> -<!ELEMENT view (component*)> Deleted: trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-dialog-config_1_0.dtd =================================================================== --- trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-dialog-config_1_0.dtd 2007-07-20 17:19:09 UTC (rev 2568) +++ trunk/shale/plugins/org.jboss.tools.shale/resources/meta/shale-dialog-config_1_0.dtd 2007-07-20 17:21:10 UTC (rev 2569) @@ -1,183 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<!-- - - Copyright 2004-2005 The Apache Software Foundation. - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - - $Id: shale-dialog-config_1_0.dtd,v 1.1 2005/12/23 14:01:34 glory Exp $ - ---> - -<!-- - - DTD for dialog definitions used by the "org.apache.shale.dialog" package. - To support validation of your configuration file, include the following - DOCTYPE element at the beginning (after the "xml" declaration): - - <!DOCTYPE dialogs PUBLIC - "-//Apache Software Foundation//DTD Shale Dialog Configuration 1.0//EN" - "http://struts.apache.org/dtds/shale-dialog-config_1_0.dtd"> - ---> - - -<!-- ====================== Top Level Elements ============================= --> - - -<!-- The "dialogs" element is the root of a single configuration file, and - contains zero or more "dialog" elements defining the states and transitions - for a particular dialog. ---> -<!ELEMENT dialogs (dialog*)> - - -<!-- The "dialog" element defines the states for a particular reusable dialog, - which itself consists of zero or more states (of particular types). The - following attributes are defined: - - className Fully qualified class name of the configuration - object for this element. - [org.apache.shale.dialog.impl.DialogImpl] - - name Name of this dialog (must be unique among - all defined dialogs). - - start Name of the starting state for this dialog. ---> -<!ELEMENT dialog ((transition|action|end|subdialog|view)*)> -<!ATTLIST dialog className CDATA #IMPLIED> -<!ATTLIST dialog name CDATA #REQUIRED> -<!ATTLIST dialog start CDATA #REQUIRED> - - -<!-- The "action" element represents an action state, which causes the - invocation of a public method that takes no arguments, and returns - the logical outcome as a String. The following attributes are defined: - - className Fully qualified class name of the configuration - object for this element. - [org.apache.shale.dialog.impl.ActionStateImpl] - - name Name of this state (must be unique among - all states defined for this dialog). - - method Method binding expression ("#{...}") that - identifies a public method that takes no - arguments, and returns a String that represents - the logical outcome of this state. ---> -<!ELEMENT action (transition*)> -<!ATTLIST action className CDATA #IMPLIED> -<!ATTLIST action name CDATA #REQUIRED> -<!ATTLIST action method CDATA #REQUIRED> - - -<!-- The "subdialog" element represents a transition to a subordinate - dialog, saving the current state in the currently executing dialog - on a stack. When the subordinate dialog completes, the outcome it - returns will be used to trigger a transition in this dialog. - The following attributes are defined: - - className Fully qualified class name of the configuration - object for this element. - [org.apache.shale.dialog.impl.SubdialogStateImpl] - - name Name of this state (must be unique among - all states defined for this dialog). - - dialogName Name of the subordinate dialog to be - executed. - ---> -<!ELEMENT subdialog (transition*)> -<!ATTLIST subdialog className CDATA #IMPLIED> -<!ATTLIST subdialog name CDATA #REQUIRED> -<!ATTLIST subdialog dialogName CDATA #REQUIRED> - - -<!-- The "view" element represents a view state, which causes the rendering - of the specified JavaServer Faces view. When the subsequent submit from - this view is returned, the outcome returned by whatever action method was - invoked is returned in order to determine the next transition. The - following attributes are defined: - - className Fully qualified class name of the configuration - object for this element. - [org.apache.shale.dialog.impl.ViewStateImpl] - - name Name of this state (must be unique among - all states defined for this dialog). - - viewId View identifier of the JavaServer Faces view - that should be rendered. The logical outcome - returned by whatever action handles the - subsequent submit from this view will be used - to determine the next state transition. - ---> -<!ELEMENT view (transition*)> -<!ATTLIST view className CDATA #IMPLIED> -<!ATTLIST view name CDATA #REQUIRED> -<!ATTLIST view viewId CDATA #REQUIRED> - - -<!-- The "end" element represents a state that terminates a dialog. If - a view identifier is specified, it is rendered; otherwise, it is assumed - that a parent dialog which invoked the current dialog will be responsible - for producing the view for the current response. - - className Fully qualified class name of the configuration - object for this element. - [org.apache.shale.dialog.impl.EndStateImpl] - - name Name of this state (must be unique among - all states defined for this dialog). - - viewId View identifier of the JavaServer Faces view - that should be rendered (if any). The logical - outcome returned by whatever action handles the - subsequent submit from this view will be - returned to the parent dialog to drive its - own state transition. ---> -<!ELEMENT end (transition*)> -<!ATTLIST end className CDATA #IMPLIED> -<!ATTLIST end name CDATA #REQUIRED> -<!ATTLIST end viewId CDATA #IMPLIED> - - -<!-- The "transition" element represents a state transition from the current - state (in which this "transition" element is nested) to a subsequent - state. The following attributes are defined: - - className Fully qualified class name of the configuration - object for this element. - [org.apache.shale.dialog.impl.TransitionImpl] - - outcome Logical outcome String returned by the invoked - method (for an "action" element), or by the - invoked action's action method (for a "view" - element). - - target State name of the state to which control should - be transitioned. Must match the "name" - attribute of a state defined in this dialog. ---> - -<!ELEMENT transition EMPTY> -<!ATTLIST transition className CDATA #IMPLIED> -<!ATTLIST transition outcome CDATA #REQUIRED> -<!ATTLIST transition target CDATA #REQUIRED> - Deleted: trunk/shale/plugins/org.jboss.tools.shale/resources/meta/spring-beans.dtd =================================================================== --- trunk/shale/plugins/org.jboss.tools.shale/resources/meta/spring-beans.dtd 2007-07-20 17:19:09 UTC (rev 2568) +++ trunk/shale/plugins/org.jboss.tools.shale/resources/meta/spring-beans.dtd 2007-07-20 17:21:10 UTC (rev 2569) @@ -1,587 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<!-- - Spring XML Beans DTD - Authors: Rod Johnson, Juergen Hoeller, Alef Arendsen, Colin Sampaleanu - - This defines a simple and consistent way of creating a namespace - of JavaBeans objects, managed by a Spring BeanFactory, read by - XmlBeanDefinitionReader (with DefaultXmlBeanDefinitionParser). - - This document type is used by most Spring functionality, including - web application contexts, which are based on bean factories. - - Each "bean" element in this document defines a JavaBean. - Typically the bean class is specified, along with JavaBean properties - and/or constructor arguments. - - Bean instances can be "singletons" (shared instances) or "prototypes" - (independent instances). Further scopes are supposed to be built on top - of the core BeanFactory infrastructure and are therefore not part of it. - - References among beans are supported, i.e. setting a JavaBean property - or a constructor argument to refer to another bean in the same factory - (or an ancestor factory). - - As alternative to bean references, "inner bean definitions" can be used. - Singleton flags of such inner bean definitions are effectively ignored: - Inner beans are typically anonymous prototypes. - - There is also support for lists, sets, maps, and java.util.Properties - as bean property types or constructor argument types. - - As the format is simple, a DTD is sufficient, and there's no need - for a schema at this point. - - XML documents that conform to this DTD should declare the following doctype: - - <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" - "http://www.springframework.org/dtd/spring-beans.dtd"> ---> - - -<!-- - The document root. A document can contain bean definitions only, - imports only, or a mixture of both (typically with imports first). ---> -<!ELEMENT beans ( - description?, - (import | alias | bean)* -)> - -<!-- - Default values for all bean definitions. Can be overridden at - the "bean" level. See those attribute definitions for details. ---> -<!ATTLIST beans default-lazy-init (true | false) "false"> -<!ATTLIST beans default-dependency-check (none | objects | simple | all) "none"> -<!ATTLIST beans default-autowire (no | byName | byType | constructor | autodetect) "no"> - -<!-- - Element containing informative text describing the purpose of the enclosing - element. Always optional. - Used primarily for user documentation of XML bean definition documents. ---> -<!ELEMENT description (#PCDATA)> - - -<!-- - Specifies an XML bean definition resource to import. ---> -<!ELEMENT import EMPTY> - -<!-- - The relative resource location of the XML bean definition file to import, - for example "myImport.xml" or "includes/myImport.xml" or "../myImport.xml". ---> -<!ATTLIST import resource CDATA #REQUIRED> - - -<!-- - Defines an alias for a bean, which can reside in a different definition file. ---> -<!ELEMENT alias EMPTY> - -<!-- - The name of the bean to define an alias for. ---> -<!ATTLIST alias name CDATA #REQUIRED> - -<!-- - The alias name to define for the bean. ---> -<!ATTLIST alias alias CDATA #REQUIRED> - - -<!-- - Defines a single (usually named) bean. - - A bean definition may contain nested tags for constructor arguments, - property values, lookup methods, and replaced methods. Mixing constructor - injection and setter injection on the same bean is explicitly supported. ---> -<!ELEMENT bean ( - description?, - (constructor-arg | property | lookup-method | replaced-method)* -)> - -<!-- - Beans can be identified by an id, to enable reference checking. - - There are constraints on a valid XML id: if you want to reference your bean - in Java code using a name that's illegal as an XML id, use the optional - "name" attribute. If neither is given, the bean class name is used as id - (with an appended counter like "#2" if there is already a bean with that name). ---> -<!ATTLIST bean id ID #IMPLIED> - -<!-- - Optional. Can be used to create one or more aliases illegal in an id. - Multiple aliases can be separated by any number of spaces or commas. ---> -<!ATTLIST bean name CDATA #IMPLIED> - -<!-- - Each bean definition must specify the fully qualified name of the class, - except if it pure serves as parent for child bean definitions. ---> -<!ATTLIST bean class CDATA #IMPLIED> - -<!-- - Optionally specify a parent bean definition. - - Will use the bean class of the parent if none specified, but can - also override it. In the latter case, the child bean class must be - compatible with the parent, i.e. accept the parent's property values - and constructor argument values, if any. - - A child bean definition will inherit constructor argument values, - property values and method overrides from the parent, with the option - to add new values. If init method, destroy method, factory bean and/or factory - method are specified, they will override the corresponding parent settings. - - The remaining settings will always be taken from the child definition: - depends on, autowire mode, dependency check, singleton, lazy init. ---> -<!ATTLIST bean parent CDATA #IMPLIED> - -<!-- - Is this bean "abstract", i.e. not meant to be instantiated itself but - rather just serving as parent for concrete child bean definitions. - Default is false. Specify true to tell the bean factory to not try to - instantiate that particular bean in any case. ---> -<!ATTLIST bean abstract (true | false) "false"> - -<!-- - Is this bean a "singleton" (one shared instance, which will - be returned by all calls to getBean() with the id), - or a "prototype" (independent instance resulting from each call to - getBean(). Default is singleton. - - Singletons are most commonly used, and are ideal for multi-threaded - service objects. ---> -<!ATTLIST bean singleton (true | false) "true"> - -<!-- - If this bean should be lazily initialized. - If false, it will get instantiated on startup by bean factories - that perform eager initialization of singletons. ---> -<!ATTLIST bean lazy-init (true | false | default) "default"> - -<!-- - Optional attribute controlling whether to "autowire" bean properties. - This is an automagical process in which bean references don't need to be coded - explicitly in the XML bean definition file, but Spring works out dependencies. - - There are 5 modes: - - 1. "no" - The traditional Spring default. No automagical wiring. Bean references - must be defined in the XML file via the <ref> element. We recommend this - in most cases as it makes documentation more explicit. - - 2. "byName" - Autowiring by property name. If a bean of class Cat exposes a dog property, - Spring will try to set this to the value of the bean "dog" in the current factory. - If there is no matching bean by name, nothing special happens; - use dependency-check="objects" to raise an error in that case. - - 3. "byType" - Autowiring if there is exactly one bean of the property type in the bean factory. - If there is more than one, a fatal error is raised, and you can't use byType - autowiring for that bean. If there is none, nothing special happens; - use dependency-check="objects" to raise an error in that case. - - 4. "constructor" - Analogous to "byType" for constructor arguments. If there isn't exactly one bean - of the constructor argument type in the bean factory, a fatal error is raised. - - 5. "autodetect" - Chooses "constructor" or "byType" through introspection of the bean class. - If a default constructor is found, "byType" gets applied. - - The latter two are similar to PicoContainer and make bean factories simple to - configure for small namespaces, but doesn't work as well as standard Spring - behaviour for bigger applications. - - Note that explicit dependencies, i.e. "property" and "constructor-arg" elements, - always override autowiring. Autowire behaviour can be combined with dependency - checking, which will be performed after all autowiring has been completed. ---> -<!ATTLIST bean autowire (no | byName | byType | constructor | autodetect | default) "default"> - -<!-- - Optional attribute controlling whether to check whether all this - beans dependencies, expressed in its properties, are satisfied. - Default is no dependency checking. - - "simple" type dependency checking includes primitives and String - "object" includes collaborators (other beans in the factory) - "all" includes both types of dependency checking ---> -<!ATTLIST bean dependency-check (none | objects | simple | all | default) "default"> - -<!-- - The names of the beans that this bean depends on being initialized. - The bean factory will guarantee that these beans get initialized before. - - Note that dependencies are normally expressed through bean properties or - constructor arguments. This property should just be necessary for other kinds - of dependencies like statics (*ugh*) or database preparation on startup. ---> -<!ATTLIST bean depends-on CDATA #IMPLIED> - -<!-- - Optional attribute for the name of the custom initialization method - to invoke after setting bean properties. The method must have no arguments, - but may throw any exception. ---> -<!ATTLIST bean init-method CDATA #IMPLIED> - -<!-- - Optional attribute for the name of the custom destroy method to invoke - on bean factory shutdown. The method must have no arguments, - but may throw any exception. Note: Only invoked on singleton beans! ---> -<!ATTLIST bean destroy-method CDATA #IMPLIED> - -<!-- - Optional attribute specifying the name of a factory method to use to - create this object. Use constructor-arg elements to specify arguments - to the factory method, if it takes arguments. Autowiring does not apply - to factory methods. - - If the "class" attribute is present, the factory method will be a static - method on the class specified by the "class" attribute on this bean - definition. Often this will be the same class as that of the constructed - object - for example, when the factory method is used as an alternative - to a constructor. However, it may be on a different class. In that case, - the created object will *not* be of the class specified in the "class" - attribute. This is analogous to FactoryBean behavior. - - If the "factory-bean" attribute is present, the "class" attribute is not - used, and the factory method will be an instance method on the object - returned from a getBean call with the specified bean name. The factory - bean may be defined as a singleton or a prototype. - - The factory method can have any number of arguments. Autowiring is not - supported. Use indexed constructor-arg elements in conjunction with the - factory-method attribute. - - Setter Injection can be used in conjunction with a factory method. - Method Injection cannot, as the factory method returns an instance, - which will be used when the container creates the bean. ---> -<!ATTLIST bean factory-method CDATA #IMPLIED> - -<!-- - Alternative to class attribute for factory-method usage. - If this is specified, no class attribute should be used. - This should be set to the name of a bean in the current or - ancestor factories that contains the relevant factory method. - This allows the factory itself to be configured using Dependency - Injection, and an instance (rather than static) method to be used. ---> -<!ATTLIST bean factory-bean CDATA #IMPLIED> - - -<!-- - Bean definitions can specify zero or more constructor arguments. - This is an alternative to "autowire constructor". - Arguments correspond to either a specific index of the constructor argument - list or are supposed to be matched generically by type. - - Note: A single generic argument value will just be used once, rather than - potentially matched multiple times (as of Spring 1.1). - - constructor-arg elements are also used in conjunction with the factory-method - element to construct beans using static or instance factory methods. ---> -<!ELEMENT constructor-arg ( - description?, - (bean | ref | idref | value | null | list | set | map | props)? -)> - -<!-- - The constructor-arg tag can have an optional index attribute, - to specify the exact index in the constructor argument list. Only needed - to avoid ambiguities, e.g. in case of 2 arguments of the same type. ---> -<!ATTLIST constructor-arg index CDATA #IMPLIED> - -<!-- - The constructor-arg tag can have an optional type attribute, - to specify the exact type of the constructor argument. Only needed - to avoid ambiguities, e.g. in case of 2 single argument constructors - that can both be converted from a String. ---> -<!ATTLIST constructor-arg type CDATA #IMPLIED> - -<!-- - A short-cut alternative to a child element "ref bean=". ---> -<!ATTLIST constructor-arg ref CDATA #IMPLIED> - -<!-- - A short-cut alternative to a child element "value". ---> -<!ATTLIST constructor-arg value CDATA #IMPLIED> - - -<!-- - Bean definitions can have zero or more properties. - Property elements correspond to JavaBean setter methods exposed - by the bean classes. Spring supports primitives, references to other - beans in the same or related factories, lists, maps and properties. ---> -<!ELEMENT property ( - description?, - (bean | ref | idref | value | null | list | set | map | props)? -)> - -<!-- - The property name attribute is the name of the JavaBean property. - This follows JavaBean conventions: a name of "age" would correspond - to setAge()/optional getAge() methods. ---> -<!ATTLIST property name CDATA #REQUIRED> - -<!-- - A short-cut alternative to a child element "ref bean=". ---> -<!ATTLIST property ref CDATA #IMPLIED> - -<!-- - A short-cut alternative to a child element "value". ---> -<!ATTLIST property value CDATA #IMPLIED> - - -<!-- - A lookup method causes the IoC container to override the given method and return - the bean with the name given in the bean attribute. This is a form of Method Injection. - It's particularly useful as an alternative to implementing the BeanFactoryAware - interface, in order to be able to make getBean() calls for non-singleton instances - at runtime. In this case, Method Injection is a less invasive alternative. ---> -<!ELEMENT lookup-method EMPTY> - -<!-- - Name of a lookup method. This method should take no arguments. ---> -<!ATTLIST lookup-method name CDATA #IMPLIED> - -<!-- - Name of the bean in the current or ancestor factories that the lookup method - should resolve to. Often this bean will be a prototype, in which case the - lookup method will return a distinct instance on every invocation. This - is useful for single-threaded objects. ---> -<!ATTLIST lookup-method bean CDATA #IMPLIED> - - -<!-- - Similar to the lookup method mechanism, the replaced-method element is used to control - IoC container method overriding: Method Injection. This mechanism allows the overriding - of a method with arbitrary code. ---> -<!ELEMENT replaced-method ( - (arg-type)* -)> - -<!-- - Name of the method whose implementation should be replaced by the IoC container. - If this method is not overloaded, there's no need to use arg-type subelements. - If this method is overloaded, arg-type subelements must be used for all - override definitions for the method. ---> -<!ATTLIST replaced-method name CDATA #IMPLIED> - -<!-- - Bean name of an implementation of the MethodReplacer interface - in the current or ancestor factories. This may be a singleton or prototype - bean. If it's a prototype, a new instance will be used for each method replacement. - Singleton usage is the norm. ---> -<!ATTLIST replaced-method replacer CDATA #IMPLIED> - -<!-- - Subelement of replaced-method identifying an argument for a replaced method - in the event of method overloading. ---> -<!ELEMENT arg-type (#PCDATA)> - -<!-- - Specification of the type of an overloaded method argument as a String. - For convenience, this may be a substring of the FQN. E.g. all the - following would match "java.lang.String": - - java.lang.String - - String - - Str - - As the number of arguments will be checked also, this convenience can often - be used to save typing. ---> -<!ATTLIST arg-type match CDATA #IMPLIED> - - -<!-- - Defines a reference to another bean in this factory or an external - factory (parent or included factory). ---> -<!ELEMENT ref EMPTY> - -<!-- - References must specify a name of the target bean. - The "bean" attribute can reference any name from any bean in the context, - to be checked at runtime. - Local references, using the "local" attribute, have to use bean ids; - they can be checked by this DTD, thus should be preferred for references - within the same bean factory XML file. ---> -<!ATTLIST ref bean CDATA #IMPLIED> -<!ATTLIST ref local IDREF #IMPLIED> -<!ATTLIST ref parent CDATA #IMPLIED> - - -<!-- - Defines a string property value, which must also be the id of another - bean in this factory or an external factory (parent or included factory). - While a regular 'value' element could instead be used for the same effect, - using idref in this case allows validation of local bean ids by the xml - parser, and name completion by helper tools. ---> -<!ELEMENT idref EMPTY> - -<!-- - ID refs must specify a name of the target bean. - The "bean" attribute can reference any name from any bean in the context, - potentially to be checked at runtime by bean factory implementations. - Local references, using the "local" attribute, have to use bean ids; - they can be checked by this DTD, thus should be preferred for references - within the same bean factory XML file. ---> -<!ATTLIST idref bean CDATA #IMPLIED> -<!ATTLIST idref local IDREF #IMPLIED> - - -<!-- - Contains a string representation of a property value. - The property may be a string, or may be converted to the - required type using the JavaBeans PropertyEditor - machinery. This makes it possible for application developers - to write custom PropertyEditor implementations that can - convert strings to objects. - - Note that this is recommended for simple objects only. - Configure more complex objects by populating JavaBean - properties with references to other beans. ---> -<!ELEMENT value (#PCDATA)> - -<!-- - The value tag can have an optional type attribute, to specify the - exact type that the value should be converted to. Only needed - if the type of the target property or constructor argument is - too generic: for example, in case of a collection element. ---> -<!ATTLIST value type CDATA #IMPLIED> - -<!-- - Denotes a Java null value. Necessary because an empty "value" tag - will resolve to an empty String, which will not be resolved to a - null value unless a special PropertyEditor does so. ---> -<!ELEMENT null (#PCDATA)> - - -<!-- - A list can contain multiple inner bean, ref, collection, or value elements. - Java lists are untyped, pending generics support in Java 1.5, - although references will be strongly typed. - A list can also map to an array type. The necessary conversion - is automatically performed by the BeanFactory. ---> -<!ELEMENT list ( - (bean | ref | idref | value | null | list | set | map | props)* -)> - -<!-- - A set can contain multiple inner bean, ref, collection, or value elements. - Java sets are untyped, pending generics support in Java 1.5, - although references will be strongly typed. ---> -<!ELEMENT set ( - (bean | ref | idref | value | null | list | set | map | props)* -)> - - -<!-- - A Spring map is a mapping from a string key to object. - Maps may be empty. ---> -<!ELEMENT map ( - (entry)* -)> - -<!-- - A map entry can be an inner bean, ref, value, or collection. - The key of the entry is given by the "key" attribute or child element. ---> -<!ELEMENT entry ( - key?, - (bean | ref | idref | value | null | list | set | map | props)? -)> - -<!-- - Each map element must specify its key as attribute or as child element. - A key attribute is always a String value. ---> -<!ATTLIST entry key CDATA #IMPLIED> - -<!-- - A short-cut alternative to a "key" element with a "ref bean=" child element. ---> -<!ATTLIST entry key-ref CDATA #IMPLIED> - -<!-- - A short-cut alternative to a child element "value". ---> -<!ATTLIST entry value CDATA #IMPLIED> - -<!-- - A short-cut alternative to a child element "ref bean=". ---> -<!ATTLIST entry value-ref CDATA #IMPLIED> - -<!-- - A key element can contain an inner bean, ref, value, or collection. ---> -<!ELEMENT key ( - (bean | ref | idref | value | null | list | set | map | props) -)> - - -<!-- - Props elements differ from map elements in that values must be strings. - Props may be empty. ---> -<!ELEMENT props ( - (prop)* -)> - -<!-- - Element content is the string value of the property. - Note that whitespace is trimmed off to avoid unwanted whitespace - caused by typical XML formatting. ---> -<!ELEMENT prop (#PCDATA)> - -<!-- - Each property element must specify its key. ---> -<!ATTLIST prop key CDATA #REQUIRED> -