Skip to Content.
Sympa Menu

notify-dpml - svn commit: r1406 - in development/main/central/site/src/docs: concepts products/transit/properties products/transit/properties/cache products/transit/properties/hosts

notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

Chronological Thread  
  • From: dleangen AT netcompartner.com
  • To: notify-dpml AT lists.ibiblio.org
  • Subject: svn commit: r1406 - in development/main/central/site/src/docs: concepts products/transit/properties products/transit/properties/cache products/transit/properties/hosts
  • Date: Sat, 08 Jan 2005 06:44:21 +0100

Author: dleangen
Date: Sat Jan 8 06:44:21 2005
New Revision: 1406

Added:
development/main/central/site/src/docs/concepts/dpml_home.xml

development/main/central/site/src/docs/products/transit/properties/cache.xml

development/main/central/site/src/docs/products/transit/properties/hosts.xml
Removed:
development/main/central/site/src/docs/products/transit/properties/cache/
development/main/central/site/src/docs/products/transit/properties/hosts/
Modified:
development/main/central/site/src/docs/concepts/index.xml

development/main/central/site/src/docs/products/transit/properties/index.xml

development/main/central/site/src/docs/products/transit/properties/navigation.xml
Log:
Updated information about Transit properties.


Added: development/main/central/site/src/docs/concepts/dpml_home.xml
==============================================================================
--- (empty file)
+++ development/main/central/site/src/docs/concepts/dpml_home.xml Sat
Jan 8 06:44:21 2005
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document verified="false">
+ <properties>
+ <author email="dleangen AT dpml.net">David Leangen</author>
+ <title>DPML Concepts</title>
+ </properties>
+
+ <body>
+ <section name="${dpml.home}">
+
+ <p role="intro">
+ Environment variable that sets the home directory for your DPML
products.
+ </p>
+
+ <p>
+ This is the notation we use throughout this documentation to refer
to the
+ environment variable "DPML_HOME".
+ </p>
+
+ <p>
+ The location ${dpml.home} defines the location of your
+ <a href="index.html#local_cache">local cache</a>, as well as many of
the
+ configuration files required by the DPML systems.
+ </p>
+
+ <p>
+ See also:
+ <ul>
+ <li><a href="../guide/setup/dpml.html">DPML setup</a></li>
+ </ul>
+ </p>
+
+ </section>
+
+ </body>
+</document>

Modified: development/main/central/site/src/docs/concepts/index.xml
==============================================================================
--- development/main/central/site/src/docs/concepts/index.xml (original)
+++ development/main/central/site/src/docs/concepts/index.xml Sat Jan 8
06:44:21 2005
@@ -21,6 +21,12 @@
<th>Meaning</th>
</tr>
<tr>
+ <td><a name="dpml_home"
href="dpml_home.html"><strong>${dpml.home}</strong></a></td>
+ <td>
+ Environment variable that sets the home directory for your
DPML products.
+ </td>
+ </tr>
+ <tr>
<td><a name="artifact" href=""><strong>artifact</strong></a></td>
<td>
</td>
@@ -36,6 +42,11 @@
</td>
</tr>
<tr>
+ <td><a name="host" href=""><strong>host</strong></a></td>
+ <td>
+ </td>
+ </tr>
+ <tr>
<td><a name="enabled_solution" href=""><strong>enabled
solution</strong></a></td>
<td>
</td>

Added:
development/main/central/site/src/docs/products/transit/properties/cache.xml
==============================================================================
--- (empty file)
+++
development/main/central/site/src/docs/products/transit/properties/cache.xml
Sat Jan 8 06:44:21 2005
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+ Copyright 2004 Niclas Hedhman
+ Copyright 2005 David Leangen
+
+ 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.dpml.net/central/about/legal/
+
+ 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.
+-->
+
+<document verified="false">
+ <properties>
+ <author email="niclas AT hedhman.org">Niclas Hedhman</author>
+ <author email="david.leangen AT konova.com">David Leangen</author>
+ <title>DPML Transit</title>
+ </properties>
+
+ <body>
+ <section name="Cache Properties">
+ <p>
+ The <a href="../../../concepts/index.html#local_cache_manager">local
cache manager</a>
+ stores the downloaded
+ <a href="../../../concepts/index.html#artifact">artifact</a>s on
your
+ local file system.
+ This allows your DPML-enabled applications to quickly retrieve
+ required resources.
+ </p>
+
+ <p>
+ When requested by your application, the cache manager will first
+ check the local cache for the required resource.
+ If the resource is not available in the local cache, the cache
manager
+ will then query each
+ <a href="../../../concepts/index.html#remote_repository">remote
repository</a>
+ defined as a
+ <a href="../../../concepts/index.html#host">host</a>
+ until the resource is found.
+ </p>
+
+ <p>
+ Requests to remote repositories are conducted sequentially in order
of
+ priority, with the highest priority value queried first.
+ </p>
+
+ &lt;&lt; insert figure &gt;&gt;
+
+ <subsection name="Properties" >
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Default Value</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td>dpml.transit.cache.location</td>
+ <td><a
href="../../../concepts/index.html#dpml_home">${dpml.home}</a>/main</td>
+ <td>The location of the cache system.</td>
+ </tr>
+ <tr>
+ <td>dpml.transit.cache.class</td>
+ <td><a
href="../../../../@TRANSIT-DOCS-PATH@/net/dpml/transit/artifact/FieldCacheHandler.html">net.dpml.transit.artifact.FileCacheHandler</a></td>
+ <td>
+ The class that implements the cache handler interface
+ <a
href="../../../../@TRANSIT-DOCS-PATH@/net/dpml/transit/artifact/CacheHandler.html">net.dpml.transit.artifact.CacheHandler</a>.
+ </td>
+ </tr>
+ </table>
+ </subsection>
+ </section>
+ </body>
+</document>
+
+
+

Added:
development/main/central/site/src/docs/products/transit/properties/hosts.xml
==============================================================================
--- (empty file)
+++
development/main/central/site/src/docs/products/transit/properties/hosts.xml
Sat Jan 8 06:44:21 2005
@@ -0,0 +1,355 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+ Copyright 2004 Niclas Hedhman
+
+ 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.dpml.net/central/about/legal/
+
+ 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.
+-->
+
+<document>
+ <properties>
+ <author email="niclas AT hedhman.org">Niclas Hedhman</author>
+ <title>DPML Transit</title>
+ </properties>
+
+ <body>
+ <section name="Hosts Configuration">
+
+ <p>
+ A Resource Host is a place where Artifacts can be downloaded. Transit
+ is capable of handling many types of resource hosts. Conceptually,
you
+ only need to implement the
+ <code>net.dpml.transit.artifact.ResourceHost</code> interface, and
+ specify the implementation class of the host handler.
+ host.
+ </p>
+
+ <p>
+ Resource hosts may be declared via XML (default) or property files.
+ </p>
+
+ <subsection name="XML Specification">
+
+ <p>
+ The hosts configuation files when full expanded contains multiple
&lt;host&gt;
+ element entries. The following example shows a host element with
all
+ elements declared:
+ </p>
+
+<source><![CDATA[
+<hosts>
+
+ <host href="http://www.dpml.net"; enabled="true">
+ <priority>20</priority>
+ <policy>fast</policy>
+ <trusted>false</trusted>
+ <class>net.dpml.transit.artifact.ClassicResourceHost</class>
+ <index href="index.idx">
+ <credentials>
+ <username>fred</username>
+ <password>blogs</password>
+ </credentials>
+ <scheme>basic</scheme>
+ <prompt>repository</prompt>
+ </host>
+
+</hosts>
+]]></source>
+
+ <p>
+ The default host configuration file is shown below, and find the
+ description of the elements in the <strong>properties</strong>
section
+ below.
+ </p>
+
+<source><![CDATA[
+<hosts>
+
+ <host dir="local/SNAPSHOT">
+ <priority>10</priority>
+ <trusted>true</trusted>
+ </host>
+
+ <host href="http://www.dpml.net/repository";>
+ <priority>20</priority>
+ </host>
+
+ <host href="http://www.ibiblio.org/maven";>
+ <priority>50</priority>
+ </host>
+
+ <host href="http://www.apache.org/dist/java-repository";>
+ <priority>70</priority>
+ </host>
+
+</hosts>]]></source>
+
+ </subsection>
+
+ <subsection name="Properties Specification">
+
+ <p>
+ If a host.xml file is not present, Transit will atempt to resolve
hosts using
+ a set of property based host descriptors. Property files describing
remote hosts
+ are based on the following property specification.
+ </p>
+
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Default Value</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.enabled</td>
+ <td>true</td>
+ <td>
+ If true, the remote host repository will be used. If false, it
+ will be skipped completely.
+ </td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.base</td>
+ <td></td>
+ <td>This defines the base URL of the remote host repository.</td>

+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.class</td>
+ <td>net.dpml.transit.artifact.ClassicResourceHost</td>
+ <td>
+ Defines the class to use for the management of the remote host.
+ </td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.knowngroups</td>
+ <td></td>
+ <td>
+ A URL pointing to a file containing a line-separated list of
+ groups that are known to be installed on the remote host
+ repository. (named &lt;index&gt; in the hosts.xml file.)
+ </td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.username</td>
+ <td></td>
+ <td>The username required for the remote host.</td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.password</td>
+ <td></td>
+ <td>The password for the user required to access the remote
host.</td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.scheme</td>
+ <td></td>
+ <td>The authentication scheme used for the connection.</td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.prompt</td>
+ <td></td>
+ <td>
+ The authentication <strong>prompt</strong> or
+ <strong>realm</strong> sent by the server.
+ </td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.policy</td>
+ <td>fast</td>
+ <td>
+ Download policy. "fast"=if the artifact exist in the cache, use
+ it.
+ </td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.priority</td>
+ <td>80</td>
+ <td>
+ The priority defines which host should take precedence over
+ another host for obtaining the artifact. A lower number indicates
+ a higher priority.
+ </td>
+ </tr>
+ <tr>
+ <td>dpml.transit.resourcehost.trusted</td>
+ <td>false</td>
+ <td>
+ If true Transit shall assume that the host connection is trusted.
+ When set to "true" in conjunction with an https:// conection,
the
+ certificate chain of the host will be accepted unconditionally.
+ </td>
+ </tr>
+ <!--
+ <tr>
+ <td>dpml.transit.resourcehost.upload</td>
+ <td>false</td>
+ <td>
+ Upload policy. If true, writing a versioned artifact to its
+ output stream will also initiate an attempt to upload that
+ artifact to the remote host. SCP will be used, and username and
+ password will be used from the above property settings.
+ </td>
+ <td>Not Implemented</td>
+ </tr>
+ -->
+ </table>
+
+ </subsection>
+
+ <subsection name="Authorative Host">
+
+ <p>
+ The Transit system may be configured locally or remotely depending on
+ the value of the "dpml.transit.authority" property. The property
identifies
+ a remote or local path to the authorative configuration and is held
within a
+ file of the same name.
+ </p>
+
+ <p>Search sequence:</p>
+
+ <ol>
+ <li><code>${java.ext.dirs}/dpml.transit.authority</code></li>
+ <li><code>${dpml.home}/transit/dpml.transit.authority</code></li>
+ </ol>
+
+ <p>
+ In the "dpml.transit.authority" file, a single property
+ "dpml.transit.authority" is resolved to a URL of the
+ Authorative Host. If no protocol is given, it is assumed to be a
+ directory in the local file system relative to
+ <i>${dpml.home}/transit</i>.
+ </p>
+
+ <p>Default contents of dpml.transit.authority file:</p>
+
+<source>
+dpml.transit.authority=authority/
+</source>
+
+ <p>The default value of the above is equivalent to:</p>
+
+<pre>
+ ${dpml.home}/transit/authority/
+</pre>
+
+ <p>
+ The configuration of available hosts is contained in the file:
+ </p>
+<pre>
+ ${dpml.transit.authority}/hosts.xml
+</pre>
+
+ <p>
+ Transit will also look for property based host descriptors. If the
+ value of ${dpml.transit.authority} is a file url host properties
files
+ will be resolved relative to the following path:
+ </p>
+
+<pre>
+ ${dpml.transit.authority}/hosts/*.*
+</pre>
+ <p>
+ All files found in the hosts/ directory will be read one by one.
+ The priority property will determine in which order the hosts are
+ queried for artifacts.
+ </p>
+ <p>
+ If the location is a remote URL, it will read the file
+ "index.lst" at that location. "index.lst" must contain a line
+ separated list of files that can be read at the location,
containing
+ the resource host defintions.
+ </p>
+
+ </subsection>
+
+ <!--
+ <subsection name="Properties" >
+ <p>
+ The following properties must be located in the file authorative
host
+ configuration file, default file location is
+ ${dpml.home}/transit/authority/transit.conf
+ </p>
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Default Value</th>
+ <th>Description</th>
+ <th>Note</th>
+ </tr>
+ <tr>
+ <td>dpml.transit.authority.checksum.required</td>
+ <td>false</td>
+ <td>
+ If true, artifacts that doesn't have a valid checksum will not
be
+ loaded.
+ </td>
+ <td><strong>Not Implemented.</strong></td>
+ </tr>
+ <tr>
+ <td>dpml.authority.checksum.from.trusted</td>
+ <td>true</td>
+ <td>
+ If true, checksums will only be downloaded from the trusted
+ repository hosts. This increases the security against spoofed
+ codebases, by ensuring that the checksum of trusted host
matches
+ the downloaded artifact from the non-trusted host. NOTE! It is
+ still possible (although difficult) to create a codebase
artifact
+ with a matching checksum, so for better security, please use
+ signed codebases and a web of trust or a CA.
+ </td>
+ <td><strong>Not Implemented.</strong></td>
+ </tr>
+ <tr>
+ <td>dpml.transit.authority.signature.required</td>
+ <td>false</td>
+ <td>
+ If true, artifacts must be signed or the artifact will not
+ be loaded. PGP signatures is the default requirement, but
+ other signature system should be supported in the future.
+ Signatures increases the trust level by many magnitudes. By
+ installing signed keys it is fairly easy to establish a web of
+ trust, without spending money on expensive certificates.
+ </td>
+ <td><strong>Not Implemented.</strong></td>
+ </tr>
+ <tr>
+ <td>dpml.transit.authority.signature.anonymous.allow</td>
+ <td>false</td>
+ <td>
+ If true, anonymous signatures will be allowed. Anonymous
+ signatures are those that does not belong in the web of trust
+ nor lead to a known CA.
+ </td>
+ <td><strong>Not Implemented.</strong></td>
+ </tr>
+ <tr>
+ <td>dpml.transit.authority.signature.from.trusted</td>
+ <td>true</td>
+ <td>
+ If true, signatures will only be downloaded from the trusted
+ repository hosts. This increases the security, especially if
+ anonymous signatures are allowed, to ensure that code bases
are
+ not spoofed.
+ </td>
+ <td><strong>Not Implemented.</strong></td>
+ </tr>
+ </table>
+ </subsection>
+ -->
+
+ </section>
+ </body>
+</document>
+
+
+

Modified:
development/main/central/site/src/docs/products/transit/properties/index.xml
==============================================================================
---
development/main/central/site/src/docs/products/transit/properties/index.xml
(original)
+++
development/main/central/site/src/docs/products/transit/properties/index.xml
Sat Jan 8 06:44:21 2005
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
- Copyright 2004 Niclas Hedhman
+ Copyright 2004 Niclas Hedhman
+ Copyright 2005 David Leangen

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -17,157 +18,30 @@
limitations under the License.
-->

-<document>
+<document verified="false">
<properties>
<author email="niclas AT hedhman.org">Niclas Hedhman</author>
+ <author email="david.leangen AT konova.com">David Leangen</author>
<title>DPML Transit</title>
</properties>

<body>

<section name="Transit Properties">
-
- <subsection name="Authorative Host">
-
- <p>
- The Transit system may be configured locally or remotely depending on
- the value of the "dpml.transit.authority" property. The property
identifies
- a remote or local path to the authorative configuration and is held
within a
- file of the same name.
- </p>
-
- <p>Search sequence:</p>
-
- <ol>
- <li><code>${java.ext.dirs}/dpml.transit.authority</code></li>
- <li><code>${dpml.home}/transit/dpml.transit.authority</code></li>
- </ol>
-
- <p>
- In the "dpml.transit.authority" file, a single property
- "dpml.transit.authority" is resolved to a URL of the
- Authorative Host. If no protocol is given, it is assumed to be a
- directory in the local file system relative to
- <i>${dpml.home}/transit</i>.
- </p>
-
- <p>Default contents of dpml.transit.authority file:</p>
-
-<source>
-dpml.transit.authority=authority/
-</source>
-
- <p>The default value of the above is equivalent to:</p>
-
-<pre>
- ${dpml.home}/transit/authority/
-</pre>
-
- <p>
- The configuration of available hosts is contained in the file:
- </p>
-<pre>
- ${dpml.transit.authority}/hosts.xml
-</pre>
-
- <p>
- Transit will also look for property based host descriptors. If the
- value of ${dpml.transit.authority} is a file url host properties
files
- will be resolved relative to the following path:
- </p>
-
-<pre>
- ${dpml.transit.authority}/hosts/*.*
-</pre>
- <p>
- All files found in the hosts/ directory will be read one by one.
- The priority property will determine in which order the hosts are
- queried for artifacts.
- </p>
- <p>
- If the location is a remote URL, it will read the file
- "index.lst" at that location. "index.lst" must contain a line
- separated list of files that can be read at the location,
containing
- the resource host defintions.
- </p>
-
- </subsection>
+
+ <p>
+ Transit provides several configuration properties.
+ </p>
+
+ <p>
+ You can define your own configuration for:
+ <ul>
+ <li><a href="cache.html">your local cache</a></li>
+ <li><a href="hosts.html">remote hosts</a></li>
+ <li><a href="runtime.html">runtime properties</a></li>
+ </ul>
+ </p>

- <!--
- <subsection name="Properties" >
- <p>
- The following properties must be located in the file authorative
host
- configuration file, default file location is
- ${dpml.home}/transit/authority/transit.conf
- </p>
- <table>
- <tr>
- <th>Property</th>
- <th>Default Value</th>
- <th>Description</th>
- <th>Note</th>
- </tr>
- <tr>
- <td>dpml.transit.authority.checksum.required</td>
- <td>false</td>
- <td>
- If true, artifacts that doesn't have a valid checksum will not
be
- loaded.
- </td>
- <td><strong>Not Implemented.</strong></td>
- </tr>
- <tr>
- <td>dpml.authority.checksum.from.trusted</td>
- <td>true</td>
- <td>
- If true, checksums will only be downloaded from the trusted
- repository hosts. This increases the security against spoofed
- codebases, by ensuring that the checksum of trusted host
matches
- the downloaded artifact from the non-trusted host. NOTE! It is
- still possible (although difficult) to create a codebase
artifact
- with a matching checksum, so for better security, please use
- signed codebases and a web of trust or a CA.
- </td>
- <td><strong>Not Implemented.</strong></td>
- </tr>
- <tr>
- <td>dpml.transit.authority.signature.required</td>
- <td>false</td>
- <td>
- If true, artifacts must be signed or the artifact will not
- be loaded. PGP signatures is the default requirement, but
- other signature system should be supported in the future.
- Signatures increases the trust level by many magnitudes. By
- installing signed keys it is fairly easy to establish a web of
- trust, without spending money on expensive certificates.
- </td>
- <td><strong>Not Implemented.</strong></td>
- </tr>
- <tr>
- <td>dpml.transit.authority.signature.anonymous.allow</td>
- <td>false</td>
- <td>
- If true, anonymous signatures will be allowed. Anonymous
- signatures are those that does not belong in the web of trust
- nor lead to a known CA.
- </td>
- <td><strong>Not Implemented.</strong></td>
- </tr>
- <tr>
- <td>dpml.transit.authority.signature.from.trusted</td>
- <td>true</td>
- <td>
- If true, signatures will only be downloaded from the trusted
- repository hosts. This increases the security, especially if
- anonymous signatures are allowed, to ensure that code bases
are
- not spoofed.
- </td>
- <td><strong>Not Implemented.</strong></td>
- </tr>
- </table>
- </subsection>
- -->
-
</section>
</body>
</document>

Modified:
development/main/central/site/src/docs/products/transit/properties/navigation.xml
==============================================================================
---
development/main/central/site/src/docs/products/transit/properties/navigation.xml
(original)
+++
development/main/central/site/src/docs/products/transit/properties/navigation.xml
Sat Jan 8 06:44:21 2005
@@ -25,8 +25,8 @@
<body>

<menu>
- <item name="Cache Properties" href="cache/index.html"/>
- <item name="Host Config Properties" href="hosts/index.html"/>
+ <item name="Cache Properties" href="cache.html"/>
+ <item name="Host Config Properties" href="hosts.html"/>
<item name="Runtime Properties" href="runtime.html"/>
</menu>




  • svn commit: r1406 - in development/main/central/site/src/docs: concepts products/transit/properties products/transit/properties/cache products/transit/properties/hosts, dleangen, 01/08/2005

Archive powered by MHonArc 2.6.24.

Top of Page