Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4F35B200B2A for ; Fri, 10 Jun 2016 16:16:28 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4DE0D160A38; Fri, 10 Jun 2016 14:16:28 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 05538160A5E for ; Fri, 10 Jun 2016 16:16:25 +0200 (CEST) Received: (qmail 238 invoked by uid 500); 10 Jun 2016 14:16:25 -0000 Mailing-List: contact commits-help@zest.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zest.apache.org Delivered-To: mailing list commits@zest.apache.org Received: (qmail 229 invoked by uid 99); 10 Jun 2016 14:16:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jun 2016 14:16:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A70011A03FE for ; Fri, 10 Jun 2016 14:16:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.374 X-Spam-Level: X-Spam-Status: No, score=0.374 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id AtpuCiVPiZHY for ; Fri, 10 Jun 2016 14:16:10 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 8EFE85FB33 for ; Fri, 10 Jun 2016 14:16:09 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B603AE104D for ; Fri, 10 Jun 2016 14:16:07 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id CF5F83A1C62 for ; Fri, 10 Jun 2016 14:16:06 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r1747714 [6/8] - /zest/site/content/java/develop/ Date: Fri, 10 Jun 2016 14:16:05 -0000 To: commits@zest.apache.org From: niclas@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160610141606.CF5F83A1C62@svn01-us-west.apache.org> archived-at: Fri, 10 Jun 2016 14:16:28 -0000 Modified: zest/site/content/java/develop/library-locking.html URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/library-locking.html?rev=1747714&r1=1747713&r2=1747714&view=diff ============================================================================== --- zest/site/content/java/develop/library-locking.html (original) +++ zest/site/content/java/develop/library-locking.html Fri Jun 10 14:16:04 2016 @@ -67,7 +67,7 @@
Zest™
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glossary 
Overview
Groovy Scripting
Javascript Scripting
Scala Support
Alarms
Circuit Breaker
Constraints
Conversion - DEPRECATED
Event Sourcing
FileConfig
HTTP
Invocation Cache
JMX
Locking
Logging
Metrics Library
OSGi
RDF
ReST Client
ReST - HATEOAS Primer
ReST Common
ReST Server
Restlet Support
Scheduler
Servlet
Shiro Security
Shiro Web Security
Spring Integration
SQL
UID
UoWFile

Locking

code

docs

tests

The Locking Library is a simple way to mark method with Read or Write locks, and the details is handled by this -library.

This library is heavily used in EntityStore implementations.

Table 36. Artifact

Group IDArtifact IDVersion

org.apache.zest.library

org.apache.zest.library.locking

0


The library creates a java.util.concurrent.ReentrantReadWriteLock which is shared for all methods within the +library.

This library is heavily used in EntityStore implementations.

Table 36. Artifact

Group IDArtifact IDVersion

org.apache.zest.library

org.apache.zest.library.locking

0


The library creates a java.util.concurrent.ReentrantReadWriteLock which is shared for all methods within the composite. It then acquires the read or write lock in a concern that is applied to the methods of the composite, which have the corresponding annotations.

@ReadLock

This annotation will apply the ReadLockConcern to the method, and acquire the lock.readLock() on entry and relase it on exit of the method. See the ReentrantReadWriteLock for details on how/when to use it and the exact semantics.

@WriteLock

This annotation will apply the WriteLockConcern to the method, and acquire the lock.writeLock() on entry and relase Modified: zest/site/content/java/develop/library-logging.html URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/library-logging.html?rev=1747714&r1=1747713&r2=1747714&view=diff ============================================================================== --- zest/site/content/java/develop/library-logging.html (original) +++ zest/site/content/java/develop/library-logging.html Fri Jun 10 14:16:04 2016 @@ -83,7 +83,7 @@ not only different, but if not handled p to turning off whole or parts of the domain logging by mistake. We want to avoid this, and instead crystalize the needs for each scenario and audience.

Another drastic difference from previous frameworks is that we don’t have an Appender notion. All messages are entities which are stored in a configured entity store. This means that especially the domain log can be more easily be given a -user interface suitable for the domain, without complex parsing of message strings

Table 37. Artifact

Group IDArtifact IDVersion

org.apache.zest.library

org.apache.zest.library.logging

0


Logging

Logging is still not finalized and will need a lot more thought before considered done.

Debugging

To produce debugging output in your code you just need to add the field

@Optional @This Debug debug;
+user interface suitable for the domain, without complex parsing of message strings
Table 37. Artifact
Group IDArtifact IDVersion
org.apache.zest.library
org.apache.zest.library.logging
0

Logging
Logging is still not finalized and will need a lot more thought before considered done.
Debugging
To produce debugging output in your code you just need to add the field
@Optional @This Debug debug;
 
and then check for null at each usage
if( debug != null )
 {
     debug.debug( Debug.NORMAL, "Debugging is made easier." );

Modified: zest/site/content/java/develop/library-metrics.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/library-metrics.html?rev=1747714&r1=1747713&r2=1747714&view=diff
==============================================================================
--- zest/site/content/java/develop/library-metrics.html (original)
+++ zest/site/content/java/develop/library-metrics.html Fri Jun 10 14:16:04 2016
@@ -68,7 +68,7 @@
 
   
Zest™
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glossary 
Overview
Groovy Scripting
Javascript Scripting
Scala Support
Alarms
Circuit Breaker
Constraints
Conversion - DEPRECATED
Event Sourcing

 FileConfig
HTTP
Invocation Cache
JMX
Locking
Logging
Metrics Library
OSGi
RDF
ReST Client
ReST - HATEOAS Primer
ReST Common
ReST Server
Restlet Support
Scheduler
Servlet
Shiro Security
Shiro Web Security
Spring Integration
SQL
UID
UoWFile
Metrics Library
<
 /div>
The Metrics library is available to application code to get production metrics from their applications. It allows
 applications to easily mark critical section for metrics gathering, without handling the details with the Metrics
-Extension.
Table 38. Artifact
Group IDArtifact IDVersion
org.apache.zest.library
org.apache.zest.library.metrics
0

Usage
There are currently the following possibilities available;