tamaya-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anat...@apache.org
Subject [1/4] incubator-tamaya git commit: Minor additions on usage and spelling.
Date Tue, 21 Jul 2015 21:50:42 GMT
Repository: incubator-tamaya
Updated Branches:
  refs/heads/master 34ffd1906 -> 910c69fa5


Minor additions on usage and spelling.


Project: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/commit/68c715fd
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/tree/68c715fd
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/diff/68c715fd

Branch: refs/heads/master
Commit: 68c715fd901764d1bfa6a058f940562d1ee7449c
Parents: 34ffd19
Author: anatole <atsticks@gmail.com>
Authored: Sun Jul 12 18:12:37 2015 +0200
Committer: anatole <atsticks@gmail.com>
Committed: Sun Jul 12 18:12:37 2015 +0200

----------------------------------------------------------------------
 docs/src/main/asciidoc/index.adoc       | 20 ++++++++++++++++++--
 docs/src/main/asciidoc/mod_formats.adoc |  2 +-
 2 files changed, 19 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/68c715fd/docs/src/main/asciidoc/index.adoc
----------------------------------------------------------------------
diff --git a/docs/src/main/asciidoc/index.adoc b/docs/src/main/asciidoc/index.adoc
index 5707fc5..be0ab69 100644
--- a/docs/src/main/asciidoc/index.adoc
+++ b/docs/src/main/asciidoc/index.adoc
@@ -97,6 +97,24 @@ Nevertheless there are a few things that are not part of Tamaya:
   your enterprise context, such as supported file locations, formats, overriding and filter
rules etc.
 
 
+[[WhatCanIDoEithTamaya]]
+=== And what can I do with Apache Tamaya?
+
+There are basically two main usage scenarios, which are synergetic:
+
+* In an enterprise context you can easily implement a configuration architecture for your
whole company and deploy the
+  logic as an extension module. All application development teams in your company can then
depend on this module (and the
+  basic Tamaya core implementation). As a result all applications/modules in your company
follow the same configuration
+  policy, which makes it much more simpler to move people between your teams. Similarly additional
tooling functionality
+  can help you to manage configuration on application as well as on enterprise level, e.g.
providing command line or
+  REST support to access the supported configuration entries, types and values, configuration
validation and more.
+* If you are writing an application, application component or library you can support configuration
using Tamaya by
+  adding it as an optional dependency. If done so your users/customers can use Tamaya to
connect their current enterprise
+  configuration infrastructure transparently to your code. As an example you can use Tamaya
to read your default
+  configuration files, but since Tamaya is so easily extendable, customers can deploy an
additional jar, which then
+  allows them to add their own configuration mechanisms such as databases, datagrids or REST
services.
+
+
 [[WorkingGroup]]
 === Working Group
 This work is being conducted as part of a community lead joint effort under the Apache Software
Foundation. This
@@ -191,5 +209,3 @@ Javadoc of the current Extension Modules
 === Examples
 
 A comprehensive set of examples can be found link:../examples.html[here].
-
-

http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/68c715fd/docs/src/main/asciidoc/mod_formats.adoc
----------------------------------------------------------------------
diff --git a/docs/src/main/asciidoc/mod_formats.adoc b/docs/src/main/asciidoc/mod_formats.adoc
index 02c8868..984337b 100644
--- a/docs/src/main/asciidoc/mod_formats.adoc
+++ b/docs/src/main/asciidoc/mod_formats.adoc
@@ -208,7 +208,7 @@ Nevertheless from the +ConfigurationData+ instance a more complex algorithm
can
 
 ==== Mapping xml-Files
 
-The same principal can also be applied to xml-files. Consider the following configuration
file:
+The same concept can also be applied to xml-files. Consider the following configuration file:
 
 [source,xml]
 .Example.conf


Mime
View raw message