complexType "license"
Namespace:
http://www.terracotta.org/config
Content:
complex, 2 elements
Defined:
globally in terracotta-4.xsd, see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
XML Representation Summary
<...>
   
Content: 
location × type
</...>
Content Elements (2):
location (type path),
type (type license-type)
All Direct / Indirect Based Elements (1):
license (type license)
Known Usage Locations
XML Source
<xs:complexType name="license">
<xs:all>
<xs:element name="location" type="path">
<xs:annotation>
<xs:documentation>
Where is the license file? Each server must have
access to this file (which may be a relative or
absolute path). This item can use parameter
substitution, which allows you to insert data
like '%h' and have it expand to the current
hostname; this allows flexibility in the case
where different servers have their license file
in different locations.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element default="none" name="type" type="license-type">
<xs:annotation>
<xs:documentation>
What type of license is in use? This can be
'trial' or 'production', and does not affect the
behavior of the system other than ensuring that
the license in use matches this type. (This
prevents you from accidentally putting a trial
license onto your production server and then
panicking thirty days later when that license
expires.)
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:all>
</xs:complexType>
Content Element Detail
location
Where is the license file? Each server must have access to this file (which may be a relative or absolute path). This item can use parameter substitution, which allows you to insert data like '%h' and have it expand to the current hostname; this allows flexibility in the case where different servers have their license file in different locations.
Type:
path, simple content
Defined:
locally, within this complexType
XML Source
<xs:element name="location" type="path">
<xs:annotation>
<xs:documentation>
Where is the license file? Each server must have
access to this file (which may be a relative or
absolute path). This item can use parameter
substitution, which allows you to insert data
like '%h' and have it expand to the current
hostname; this allows flexibility in the case
where different servers have their license file
in different locations.
</xs:documentation>
</xs:annotation>
</xs:element>
type
What type of license is in use? This can be 'trial' or 'production', and does not affect the behavior of the system other than ensuring that the license in use matches this type. (This prevents you from accidentally putting a trial license onto your production server and then panicking thirty days later when that license expires.)
Type:
license-type, simple content
Default:
"none"
Defined:
locally, within this complexType
XML Source
<xs:element default="none" name="type" type="license-type">
<xs:annotation>
<xs:documentation>
What type of license is in use? This can be
'trial' or 'production', and does not affect the
behavior of the system other than ensuring that
the license in use matches this type. (This
prevents you from accidentally putting a trial
license onto your production server and then
panicking thirty days later when that license
expires.)
</xs:documentation>
</xs:annotation>
</xs:element>
XML Schema documentation generated with DocFlex/XML (Kit) v1.6.2
DocFlex/XML is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else!
Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task!
Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com