jboss-as-txn_1_3.xsd 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!--
  3. ~ JBoss, Home of Professional Open Source.
  4. ~ Copyright 2011, Red Hat, Inc., and individual contributors
  5. ~ as indicated by the @author tags. See the copyright.txt file in the
  6. ~ distribution for a full listing of individual contributors.
  7. ~
  8. ~ This is free software; you can redistribute it and/or modify it
  9. ~ under the terms of the GNU Lesser General Public License as
  10. ~ published by the Free Software Foundation; either version 2.1 of
  11. ~ the License, or (at your option) any later version.
  12. ~
  13. ~ This software is distributed in the hope that it will be useful,
  14. ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
  15. ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  16. ~ Lesser General Public License for more details.
  17. ~
  18. ~ You should have received a copy of the GNU Lesser General Public
  19. ~ License along with this software; if not, write to the Free
  20. ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
  21. ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
  22. -->
  23. <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
  24. targetNamespace="urn:jboss:domain:transactions:1.3"
  25. xmlns="urn:jboss:domain:transactions:1.3"
  26. elementFormDefault="qualified"
  27. attributeFormDefault="unqualified"
  28. version="1.3">
  29. <!-- The transaction subsystem root element -->
  30. <xs:element name="subsystem" type="subsystem"/>
  31. <xs:complexType name="subsystem">
  32. <xs:annotation>
  33. <xs:documentation>
  34. <![CDATA[
  35. The configuration of the transactions subsystem.
  36. ]]>
  37. </xs:documentation>
  38. </xs:annotation>
  39. <xs:sequence>
  40. <xs:element name="core-environment" type="core-environment" maxOccurs="1"/>
  41. <xs:element name="recovery-environment" type="recovery-environment" maxOccurs="1"/>
  42. <xs:element name="coordinator-environment" type="coordinator-environment" minOccurs="0" maxOccurs="1"/>
  43. <xs:element name="object-store" type="object-store" minOccurs="0" maxOccurs="1"/>
  44. <xs:element name="jts" type="jts-Type" minOccurs="0" maxOccurs="1"/>
  45. <xs:choice minOccurs="0" maxOccurs="1">
  46. <xs:element name="use-hornetq-store" type="use-hornetq-store-Type" minOccurs="0" maxOccurs="1"/>
  47. <xs:element name="jdbc-store" type="jdbc-store-Type" minOccurs="0" maxOccurs="1"/>
  48. </xs:choice>
  49. </xs:sequence>
  50. </xs:complexType>
  51. <xs:complexType name="recovery-environment">
  52. <xs:annotation>
  53. <xs:documentation>
  54. <![CDATA[
  55. The recovery environment configuration.
  56. The "socket-binding" attribute is used to reference the correct socket binding to use for the
  57. recovery environment.
  58. The "status-socket-binding" attribute is used to reference the correct socket binding to use for the
  59. transaction status manager.
  60. The "recovery-listener" attribute sets if recovery system should listen on a network socket or not.
  61. ]]>
  62. </xs:documentation>
  63. </xs:annotation>
  64. <xs:attribute name="socket-binding" type="xs:string" />
  65. <xs:attribute name="status-socket-binding" type="xs:string" />
  66. <xs:attribute name="recovery-listener" type="xs:boolean" default="false"/>
  67. </xs:complexType>
  68. <xs:complexType name="core-environment">
  69. <xs:annotation>
  70. <xs:documentation>
  71. <![CDATA[
  72. The core environment configuration.
  73. The process-id element specifies the process id implemention.
  74. The "node-identifier" attribute is used to set the node identifier on the core environment.
  75. The "path" attribute denotes a relative or absolute filesystem path denoting where the transaction
  76. manager core should store data.
  77. The "relative-to" attribute references a global path configuration in the domain model, defaulting
  78. to the JBoss Application Server data directory (jboss.server.data.dir). If the value of the "path" attribute
  79. does not specify an absolute pathname, it will treated as relative to this path.
  80. ]]>
  81. </xs:documentation>
  82. </xs:annotation>
  83. <xs:all>
  84. <xs:element name="process-id" type="process-id" />
  85. </xs:all>
  86. <xs:attribute name="node-identifier" type="xs:string" default="1"/>
  87. <xs:attribute name="path" type="xs:string" default="var"/>
  88. <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir"/>
  89. </xs:complexType>
  90. <xs:complexType name="process-id">
  91. <xs:annotation>
  92. <xs:documentation>
  93. <![CDATA[
  94. The process identifer implementation
  95. The "node-identifier" attribute is used to set the node identifier on the core environment.
  96. The "socket-process-id-max-ports" attribute is used to set the max ports on the core environment.
  97. ]]>
  98. </xs:documentation>
  99. </xs:annotation>
  100. <xs:choice>
  101. <xs:element name="uuid" type="uuid" />
  102. <xs:element name="socket" type="socket-id" />
  103. </xs:choice>
  104. </xs:complexType>
  105. <xs:complexType name="uuid">
  106. <xs:annotation>
  107. <xs:documentation>
  108. <![CDATA[
  109. The UUID based process identifer implementation
  110. ]]>
  111. </xs:documentation>
  112. </xs:annotation>
  113. </xs:complexType>
  114. <xs:complexType name="socket-id">
  115. <xs:annotation>
  116. <xs:documentation>
  117. <![CDATA[
  118. The socket based process identifer implementation
  119. The "socket-binding" attribute is used to specify the port to bind to.
  120. The "socket-process-id-max-ports" attribute is used to set the max ports on the core environment.
  121. ]]>
  122. </xs:documentation>
  123. </xs:annotation>
  124. <xs:attribute name="socket-binding" type="xs:string" use="required"/>
  125. <xs:attribute name="socket-process-id-max-ports" type="xs:int" default="10" />
  126. </xs:complexType>
  127. <xs:attribute name="socket-process-id-max-ports" type="xs:int" default="10" />
  128. <xs:complexType name="coordinator-environment">
  129. <xs:annotation>
  130. <xs:documentation>
  131. <![CDATA[
  132. The coordinator environment configuration.
  133. enable-statistics - if recording of transaction statistics is enabled, false otherwise.
  134. enable-tsm-status - if the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
  135. default-timeout - the default transaction lifetime, in seconds.
  136. ]]>
  137. </xs:documentation>
  138. </xs:annotation>
  139. <xs:attribute name="enable-statistics" type="xs:boolean" default="false"/>
  140. <xs:attribute name="enable-tsm-status" type="xs:boolean" default="false"/>
  141. <xs:attribute name="default-timeout" type="xs:int" default="300" />
  142. </xs:complexType>
  143. <xs:complexType name="object-store">
  144. <xs:annotation>
  145. <xs:documentation>
  146. <![CDATA[
  147. The object store configuration.
  148. The "path" attribute denotes a relative or absolute filesystem path denoting where the transaction
  149. manager object store should store data.
  150. The "relative-to" attribute references a global path configuration in the domain model, defaulting
  151. to the JBoss Application Server data directory (jboss.server.data.dir). If the value of the "path" attribute
  152. does not specify an absolute pathname, it will treated as relative to this path.
  153. ]]>
  154. </xs:documentation>
  155. </xs:annotation>
  156. <xs:attribute name="path" type="xs:string" default="tx-object-store"/>
  157. <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir" />
  158. </xs:complexType>
  159. <xs:complexType name="jts-Type">
  160. <xs:annotation>
  161. <xs:documentation>
  162. <![CDATA[
  163. The flag to enable JTS.
  164. ]]>
  165. </xs:documentation>
  166. </xs:annotation>
  167. </xs:complexType>
  168. <xs:complexType name="use-hornetq-store-Type">
  169. <xs:annotation>
  170. <xs:documentation>
  171. <![CDATA[
  172. The flag to enable the hornetq transaction log store.
  173. ]]>
  174. </xs:documentation>
  175. </xs:annotation>
  176. </xs:complexType>
  177. <xs:complexType name="jdbc-store-Type">
  178. <xs:annotation>
  179. <xs:documentation>
  180. <![CDATA[
  181. The presence of this tag enable the jdbc transaction log store.
  182. ]]>
  183. </xs:documentation>
  184. </xs:annotation>
  185. <xs:all>
  186. <xs:element name="action" type="jdbc-store-settings-Type" minOccurs="0" maxOccurs="1">
  187. <xs:annotation>
  188. <xs:documentation>
  189. <![CDATA[
  190. Configure jdbc store for default action store. If not present defaults are used.
  191. ]]>
  192. </xs:documentation>
  193. </xs:annotation>
  194. </xs:element>
  195. <xs:element name="communication" type="jdbc-store-settings-Type" minOccurs="0" maxOccurs="1">
  196. <xs:annotation>
  197. <xs:documentation>
  198. <![CDATA[
  199. Configure jdbc store for communication store. If not present defaults are used.
  200. ]]>
  201. </xs:documentation>
  202. </xs:annotation>
  203. </xs:element>
  204. <xs:element name="state" type="jdbc-store-settings-Type" minOccurs="0" maxOccurs="1">
  205. <xs:annotation>
  206. <xs:documentation>
  207. <![CDATA[
  208. Configure jdbc store for state store. If not present defaults are used.
  209. ]]>
  210. </xs:documentation>
  211. </xs:annotation>
  212. </xs:element>
  213. </xs:all>
  214. <xs:attribute name="datasource-jndi-name" type="xs:string" use="required">
  215. <xs:annotation>
  216. <xs:documentation>
  217. <![CDATA[
  218. Configure datasource jndi used to connect for jdbc store
  219. ]]>
  220. </xs:documentation>
  221. </xs:annotation>
  222. </xs:attribute>
  223. </xs:complexType>
  224. <xs:complexType name="jdbc-store-settings-Type">
  225. <xs:annotation>
  226. <xs:documentation>
  227. <![CDATA[
  228. Settings for jdbc store
  229. ]]>
  230. </xs:documentation>
  231. </xs:annotation>
  232. <xs:attribute name="table-prefix" type="xs:string" use="optional" />
  233. <xs:attribute name="drop-table" type="xs:boolean" use="optional" default="false"/>
  234. </xs:complexType>
  235. </xs:schema>