?? openjms.xsd
字號:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:connector="http://openjms.exolab.org/connector"
targetNamespace="http://openjms.exolab.org/configuration">
<xsd:annotation>
<xsd:documentation>
This schema describes the OpenJMS 0.7.7 configuration file used to
configure the OpenJMS server.
Author <a href="mailto:jima@comware.com.au">Jim Alateras;<a>
Author <a href="mailto:tma@netspace.net.au">Tim Anderson;<a>
Author <a href="mailto:knut@lerpold">Knut Lerpold;<a>
Created 14-Feb-2001
</xsd:documentation>
</xsd:annotation>
<xsd:import namespace="http://openjms.exolab.org/connector"
schemaLocation="connector.xsd" />
<xsd:element name="Configuration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This top level element defines the structure of the OpenJMS
configuration file.
A minimum configuration must provide details for the
DatabaseConfiguration and AdminConfiguration elements - default values
will be provided for all other elements.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="DatabaseConfiguration" />
<xsd:element ref="AdminConfiguration" />
<xsd:element ref="ServerConfiguration" minOccurs="0" />
<xsd:element ref="Connectors" minOccurs="0" />
<xsd:element ref="TcpConfiguration" minOccurs="0" />
<xsd:element ref="TcpsConfiguration" minOccurs="0" />
<xsd:element ref="RmiConfiguration" minOccurs="0" />
<xsd:element ref="HttpConfiguration" minOccurs="0" />
<xsd:element ref="HttpsConfiguration" minOccurs="0" />
<xsd:element ref="JndiConfiguration" minOccurs="0" />
<xsd:element ref="MessageManagerConfiguration" minOccurs="0" />
<xsd:element ref="SchedulerConfiguration" minOccurs="0" />
<xsd:element ref="GarbageCollectionConfiguration" minOccurs="0" />
<xsd:element ref="LoggerConfiguration" minOccurs="0" />
<xsd:element ref="SecurityConfiguration" minOccurs="0" />
<xsd:element ref="Users" minOccurs="0" />
<xsd:element ref="AdministeredDestinations" minOccurs="0" />
<xsd:element ref="connector:connectorResources" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DefaultConfiguration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This top level element defines the elements which do not need to
be configured by users, but are required by OpenJMS.
Where an element is not provided by Configuration, the default values
provided by this element will be used.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ServerConfiguration" />
<xsd:element ref="Connectors" />
<xsd:element ref="TcpConfiguration" />
<xsd:element ref="TcpsConfiguration" />
<xsd:element ref="RmiConfiguration" />
<xsd:element ref="HttpConfiguration" />
<xsd:element ref="HttpsConfiguration" />
<xsd:element ref="MessageManagerConfiguration" />
<xsd:element ref="SchedulerConfiguration" />
<xsd:element ref="GarbageCollectionConfiguration" />
<xsd:element ref="LoggerConfiguration" />
<xsd:element ref="SecurityConfiguration" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ServerConfiguration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This element defines items specific to the OpenJMS server.
By default, OpenJMS uses an embedded JNDI server.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="host" type="xsd:string" use="optional"
default="localhost">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The host address of the OpenJMS server. This will typically be
'localhost'. If the host machine has multiple NICs, then
the host will need to be specified.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="embeddedJNDI" type="xsd:boolean" use="optional"
default="true">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This specifies whether to use an embedded (or internal) JNDI
provider, or an external one. If false, then the
JndiConfiguration element is relevant. For an embedded JNDI,
the JndiConfiguration element will be populated with values.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Connectors">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Connector" minOccurs="1" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Connector">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This specifies the type of communication to use, between clients
and the server.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ConnectionFactories" />
</xsd:sequence>
<xsd:attribute name="scheme" type="connector:schemeType"
use="required" />
</xsd:complexType>
</xsd:element>
<xsd:element name="TcpConfiguration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This element defines items specific to the TCP connector.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="TcpConfigurationType" />
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="TcpsConfiguration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This element defines items specific to the TCPS connector.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="TcpConfigurationType">
<xsd:attribute name="keyStore" type="xsd:string" use="optional"
default="${openjms.home}/config/openjms.keystore">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The path to the keystore.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="keyStorePassword" type="xsd:string"
use="optional" default="openjms">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The keystore password.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="keyStoreType" type="xsd:string" use="optional"
default="JKS">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The keystore type. Supported values are "JKS" and "PKCS12".
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="trustStore" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The path to the truststore. If unset, this defaults to the
keystore path.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="trustStorePassword" type="xsd:string"
use="optional">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The truststore password. If unset, this defaults to the value
of keystorePassword.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="trustStoreType" type="xsd:string" use="optional"
default="JKS">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The truststore type. Supported values are "JKS" and "PKCS12".
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="needClientAuth" type="xsd:boolean" use="optional"
default="false">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Determines if connections which are accepted must include client
authentication. By default, clients do not need to provide
authentication information.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="SocketConfigurationType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This type defines items specific to socket based connectors.
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="port" type="xsd:positiveInteger" use="required">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The port number that the server accepts connections on.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="jndiPort" type="xsd:positiveInteger" use="optional"
default="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The JNDI port, if an embedded JNDI provider is being used.
A value of zero indicates to use the same as that of the port
attribute.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="adminPort" type="xsd:positiveInteger" use="optional"
default="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The administration service port.
A value of zero indicates to use the same as that of the port
attribute.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="bindAll" type="xsd:boolean" use="optional"
default="true">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Can be used on a multi-homed host to only accept connect
requests on the address specified by ServerConfiguration/host.
If true, it will accept connections on any/all local addresses.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="maxThreads" type="xsd:positiveInteger" use="optional"
default="20">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The maximum no. of threads to use, when handling concurrent
requests. These are shared across all client connections.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexType name="TcpConfigurationType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This type defines items specific to TCP and TCPS connectors.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="SocketConfigurationType">
<xsd:attribute name="internalHost" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This is only applicable when the server is behind a NAT firewall.
This becomes the internal address the server is known by and the
host address in ServerConfiguration is the external address.
Clients will attempt to connect to ServerConfiguration/host
first. If that fails, they will try to connect to internalHost
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -