Return-Path: X-Original-To: apmail-tamaya-commits-archive@minotaur.apache.org Delivered-To: apmail-tamaya-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4C63D18697 for ; Sun, 6 Sep 2015 07:05:04 +0000 (UTC) Received: (qmail 22873 invoked by uid 500); 6 Sep 2015 07:05:04 -0000 Delivered-To: apmail-tamaya-commits-archive@tamaya.apache.org Received: (qmail 22845 invoked by uid 500); 6 Sep 2015 07:05:04 -0000 Mailing-List: contact commits-help@tamaya.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tamaya.incubator.apache.org Delivered-To: mailing list commits@tamaya.incubator.apache.org Received: (qmail 22836 invoked by uid 99); 6 Sep 2015 07:05:04 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Sep 2015 07:05:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A2792C1384 for ; Sun, 6 Sep 2015 07:05:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.78 X-Spam-Level: X-Spam-Status: No, score=0.78 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id rMe82onTOH9e for ; Sun, 6 Sep 2015 07:05:02 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 44C6E42B13 for ; Sun, 6 Sep 2015 07:05:02 +0000 (UTC) Received: (qmail 22831 invoked by uid 99); 6 Sep 2015 07:05:01 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Sep 2015 07:05:01 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 65E3CDFF1B; Sun, 6 Sep 2015 07:05:01 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: anatole@apache.org To: commits@tamaya.incubator.apache.org Message-Id: <030a687a264d48ca8098f0973b707a14@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: incubator-tamaya git commit: Fixed doc issues. Date: Sun, 6 Sep 2015 07:05:01 +0000 (UTC) Repository: incubator-tamaya Updated Branches: refs/heads/master 4f409de51 -> b81fbc1bd Fixed doc issues. Project: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/commit/b81fbc1b Tree: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/tree/b81fbc1b Diff: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/diff/b81fbc1b Branch: refs/heads/master Commit: b81fbc1bd8f20894a692f1d12ab1b8612aff5864 Parents: 4f409de Author: anatole Authored: Sun Sep 6 09:04:47 2015 +0200 Committer: anatole Committed: Sun Sep 6 09:04:47 2015 +0200 ---------------------------------------------------------------------- docs/src/main/asciidoc/mod_server.adoc | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/b81fbc1b/docs/src/main/asciidoc/mod_server.adoc ---------------------------------------------------------------------- diff --git a/docs/src/main/asciidoc/mod_server.adoc b/docs/src/main/asciidoc/mod_server.adoc index 79fd2f6..6ec84b6 100644 --- a/docs/src/main/asciidoc/mod_server.adoc +++ b/docs/src/main/asciidoc/mod_server.adoc @@ -104,9 +104,9 @@ parameters: required client configuration (for client1). Refer to the scopes section for more details. -=== Using the Configuration Servlet +=== Using the Configuration Servlets -Additionally to the fully built-in solution, it is also possible to integrate the server module with a standard +Additionally to the fully built-in solution, it is also possible to integrate the Tamaya server module with a standard Java EE servlet container. Tamaya provides 2 servlet implementations: * the servlet +org.apache.tamaya.server.FilteredConfigServlet+ can be used to register access to configurations @@ -139,7 +139,7 @@ where The server module formats the configuration returned by default in thw following variants: -.Formatting for text/json +.Formatting for +text/json+ [source, json] ----------------------------------------------- @@ -175,7 +175,7 @@ The server module formats the configuration returned by default in thw following ----------------------------------------------- -.Formatting for application/xml +.Formatting for +application/xml+ [source, xml] ----------------------------------------------- @@ -211,7 +211,7 @@ The server module formats the configuration returned by default in thw following ----------------------------------------------- -.Formatting for text/plain +.Formatting for +text/plain+ [source, text] ----------------------------------------------- @@ -247,7 +247,7 @@ Configuration: ----------------------------------------------- -.Formatting for application/html +.Formatting for +application/html+ [source, html] ----------------------------------------------- @@ -329,8 +329,10 @@ have to add the following to +META-INF/services/org.apache.tamaya.server.spi.Sco my.full.packagename.ClientScopeProvider ----------------------------------------------- -=== Finally the effective readong and configuration handlinh logic can also be replaced or improved. This can be -done by registering your own implementation of the interface ++: +==== Adapting the Way Configuration is Derived + +Finally the effective readong and configuration handling logic can also be replaced or improved. This can be +done by registering your own implementation of the interface +ConfigProviderService+: [source, java] ------------------------------------------------ @@ -346,7 +348,7 @@ By default the +ServiceContextManager+ uses the +java.util.ServiceLoader+ for co default server code you must register a higher +@Priority+ implementation. -==== Default Server +==== Replacing the Built-In Server We have seen earlier that starting a configuration server is pretty easy: @@ -369,6 +371,7 @@ public interface Server { } ----------------------------------------------- +==== The ScopeManager Singleton Finally whe implementing your own server, you might also benefit from the +ScopeManager+ singleton. Basically this class loads all registered +ScopeProvider+ and manages the configured scope instances: