org.json ValueSerialization

code
docs
tests
ValueSerialization Service backed by org.json.
TableÂ 55.Â Artifact
Group ID	Artifact ID	Version
org.apache.zest.extension	org.apache.zest.extension.valueserialization-orgjson	3.0-SNAPSHOT
Assembly

Assembly is done as follows:
@Override
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
org.json ValueSerialization
Jackson ValueSerialization
StAX ValueSerialization
Ehcache Cache
Memcache Cache
Memory EntityStore
File EntityStore
Hazelcast EntityStore
JClouds EntityStore
JDBM EntityStore
LevelDB EntityStore
MongoDB EntityStore
Preferences EntityStore
Redis EntityStore
Riak EntityStore
SQL EntityStore
ElasticSearch Index/Query
O
 penRDF Index/Query
Apache Solr Index/Query
SQL Index/Query
Yammer Metrics
Migration
Reindexer
org.json ValueSerialization
code
docs
tests
ValueSerialization Service backed by org.json.
TableÂ 55.Â Artifact
Group ID Artifact ID Version
org.apache.zest.extension org.apache.zest.extension.valueserialization-orgjson 0

Assembly
Assembly is done as follows:
@Override
 public void assemble( ModuleAssembly module )
     throws AssemblyException
 {

Modified: zest/site/content/java/develop/extension-vs-stax.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/extension-vs-stax.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/extension-vs-stax.html (original)
+++ zest/site/content/java/develop/extension-vs-stax.html Fri Apr 15 08:28:56 2016
@@ -66,7 +66,7 @@
   })();
  
 
-  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
org.json ValueSerialization
Jackson ValueSerialization
StAX ValueSerialization
Ehcache Cache
Memcache Cache
Memory EntityStore
File EntityStore
Hazelcast EntityStore
JClouds EntityStore
JDBM EntityStore
LevelDB EntityStore
MongoDB EntityStore
Preferences EntityStore
Redis EntityStore
Riak EntityStore
SQL EntityStore
ElasticSearch Index/Query
O
 penRDF Index/Query
Apache Solr Index/Query
SQL Index/Query
Yammer Metrics
Migration
Reindexer
StAX ValueSerialization
code
docs
tests
ValueSerialization Service backed by StAX<
 /a>.
TableÂ 57.Â Artifact
Group ID Artifact ID Version
org.apache.zest.extension org.apache.zest.extension.valueserialization-stax 3.0-SNAPSHOT

Assembly
Assembly is done as follows:
@Override
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
org.json ValueSerialization
Jackson ValueSerialization
StAX ValueSerialization
Ehcache Cache
Memcache Cache
Memory EntityStore
File EntityStore
Hazelcast EntityStore
JClouds EntityStore
JDBM EntityStore
LevelDB EntityStore
MongoDB EntityStore
Preferences EntityStore
Redis EntityStore
Riak EntityStore
SQL EntityStore
ElasticSearch Index/Query
O
 penRDF Index/Query
Apache Solr Index/Query
SQL Index/Query
Yammer Metrics
Migration
Reindexer
StAX ValueSerialization
code
docs
tests
ValueSerialization Service backed by StAX<
 /a>.
TableÂ 57.Â Artifact
Group ID Artifact ID Version
org.apache.zest.extension org.apache.zest.extension.valueserialization-stax 0

Assembly
Assembly is done as follows:
@Override
 public void assemble( ModuleAssembly module )
     throws AssemblyException
 {

Modified: zest/site/content/java/develop/howto-assemble-application.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-assemble-application.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-assemble-application.html (original)
+++ zest/site/content/java/develop/howto-assemble-application.html Fri Apr 15 08:28:56 2016
@@ -68,7 +68,7 @@
 
   
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial
Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Assemble an Application
We receive a lot of questions about how applications should be assembled, and since we donât have any XML to "fill in"
 and everything is to be done programmatically, it escalates the need to provide more hands-on explanation of how this is
-done.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 4.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3.0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Basics
First letâs recap the structural requirements of Zest;

+done.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 4.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutori
 al for details.
Basics
First letâs recap the structural requirements of Zest;

 There is one and only one Application instance per Zestâ¢ Runtime.
 

 Every Application must contain one or more Layers.

Modified: zest/site/content/java/develop/howto-configure-service.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-configure-service.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-configure-service.html (original)
+++ zest/site/content/java/develop/howto-configure-service.html Fri Apr 15 08:28:56 2016
@@ -70,7 +70,7 @@
 readable, writeable and queryable, just like other Entities. This should make Configuration management much simpler,
 since you can easily build GUI tools to allow editing of these in runtime. However, to simplify the initial values of
 the Configuration instance, Zestâ¢ also does the initial bootstrapping of the Configuration entity for you. This HowTo is
-going to show how.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 13.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3.0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in
  your build tutorial for details.
We need a Service
To illustrate these features we create an TravelPlan service, which allows clients to find and make Reservations to
+going to show how.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 13.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your bu
 ild tutorial for details.
We need a Service
To illustrate these features we create an TravelPlan service, which allows clients to find and make Reservations to
 Destinations. For the sake of simplicity, we are leaving out the domain detailsâ¦
public interface TravelPlan
 {
     // Domain methods, which are beyond the discussion at hand.

Modified: zest/site/content/java/develop/howto-contextual-fragments.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-contextual-fragments.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-contextual-fragments.html (original)
+++ zest/site/content/java/develop/howto-contextual-fragments.html Fri Apr 15 08:28:56 2016
@@ -70,7 +70,7 @@
 present in the composite declarations, but a start-up decision what should be added. Once the application instance is
 created, it is no longer possible to modify which fragments are attached.
Typical use-case is tracing and debugging. Other potential uses are additional security or context interfaces needing
 access to internal mixins not originally intended for, such as GUI frameworks doing reflection on certain composites.
-We strongly recommend against using this feature, as it is not needed as commonly as you may think.
Note
Constraints are not supported to be contextual at the moment.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 7.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3
 .0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
The mixins, sideeffects and concerns are added during the bootstrap phase. It is very straight-forward;
public class TraceAll
+We strongly recommend against using this feature, as it is not needed as commonly as you may think.
Note
Constraints are not supported to be contextual at the moment.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 7.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap <
 p>0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
The mixins, sideeffects and concerns are added during the bootstrap phase. It is very straight-forward;
public class TraceAll
 {
     public void assemble( ModuleAssembly module )
             throws AssemblyException

Modified: zest/site/content/java/develop/howto-create-concern.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-create-concern.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-create-concern.html (original)
+++ zest/site/content/java/develop/howto-create-concern.html Fri Apr 15 08:28:56 2016
@@ -66,7 +66,7 @@
   })();
  
 
-  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create a Concern
Concerns are defined in Concern.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 10.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3.0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Typed Concern
A typed Concern is a Java class that implements the MixinType it can be used on:
public class InventoryConcern extends ConcernOf<Order>
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create a Concern
Concerns are defined in Concern.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 10.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Typed Concern
A typed Concern is a Java class that implements the MixinType it can be used on:
public class InventoryConcern extends ConcernOf<Order>
     implements Order
 {
     @Service

Modified: zest/site/content/java/develop/howto-create-constraint.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-create-constraint.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-create-constraint.html (original)
+++ zest/site/content/java/develop/howto-create-constraint.html Fri Apr 15 08:28:56 2016
@@ -66,7 +66,7 @@
   })();
  
 
-  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create a Constraint
Constraints are defined in Constraint.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 9.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3.0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Method Constraint
Method Constraints are declared with annotations on the method argument. The annotation itself is custom, and it is possible to make your own.
public interface Dialer
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create a Constraint
Constraints are defined in Constraint.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 9.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Method Constraint
Method Constraints are declared with annotations on the method argument. The annotation itself is custom, and it is possible to make your own.
public interface Dialer
 {
     void callPhoneNumber(@PhoneNumber String phoneNo);
 

Modified: zest/site/content/java/develop/howto-create-entity.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-create-entity.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-create-entity.html (original)
+++ zest/site/content/java/develop/howto-create-entity.html Fri Apr 15 08:28:56 2016
@@ -68,7 +68,7 @@
 
   
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create an Entity
One of the most common tasks in Zestâ¢ is the management of the life cycle of Entities. Since Zestâ¢ is capable of
 delivering much higher performance than traditional Object-Relational Mapping technologies, we also expect that people
-use Entities more frequently in Zestâ¢ applications, so it is a very important topic to cover.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 12.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3.0-SNAPSHOT

Moreover, youâll need an EntityStore for persistence and an Indexing engine for querying. Choo
 se among the available
+use Entities more frequently in Zestâ¢ applications, so it is a very important topic to cover.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 12.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 0

Moreover, youâll need an EntityStore for persistence and an Indexing engine for querying. Choose among
  the available
 implementations listed in the Extensions section.
At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Basics First
All Entity operations MUST be done within a UnitOfWork. UnitOfWorks can be nested and if underlying UnitOfWorks are not
 completed (method complete()), then none of the operations will be persisted permanently.
Entity composites are subtypes of the EntityComposite interface.
Domain code typically donât need to know of the EntityComposite types directly, and is instead using the domain specific
 interface. The Visibility rules will be applied to associate the right EntityComposite when a domain type is requested.
@@ -145,26 +145,27 @@ public interface CarEntityFactoryService
         extends CarEntityFactory, ServiceComposite
 {}
 
Then we need an implementation of the mixin.
public class CarEntityFactoryMixin
-        implements CarEntityFactory
+    implements CarEntityFactory
 {
 
 
And doing that, first of all we need to request Zestâ¢ runtime to give us the Module
 that our code belongs to, and the UnitOfWork current context the execution is happening in.
Injections that are related to the Visibility rules are handled by the @Structure annotation. And the easiest way for us
 to obtain a Module is simply to;
public class CarEntityFactoryMixin
-        implements CarEntityFactory
+    implements CarEntityFactory
 {
 
     @Structure
-    Module module;
+    UnitOfWorkFactory unitOfWorkFactory;
+
 
Here Zestâ¢ will inject the member module with the correct Module. In case we only need the Module
-during the construction, we can also request it in the same manner as constructor argument.
public CarEntityFactoryMixin( @Structure Module module )
+during the construction, we can also request it in the same manner as constructor argument.
public CarEntityFactoryMixin( @Structure UnitOfWorkFactory unitOfWorkFactory )
 {
 }
 
 
This is important to know, since the injected member will not be available until AFTER the constructor has been
-completed.
We then need to provide the implementation for the create() method.
public Car create(Manufacturer manufacturer, String model)
+completed.
We then need to provide the implementation for the create() method.
public Car create( Manufacturer manufacturer, String model )
 {
-    UnitOfWork uow = module.currentUnitOfWork();
+    UnitOfWork uow = unitOfWorkFactory.currentUnitOfWork();
     EntityBuilder<Car> builder = uow.newEntityBuilder( Car.class );
 
     Car prototype = builder.instance();

Modified: zest/site/content/java/develop/howto-create-sideeffect.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-create-sideeffect.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-create-sideeffect.html (original)
+++ zest/site/content/java/develop/howto-create-sideeffect.html Fri Apr 15 08:28:56 2016
@@ -66,7 +66,7 @@
   })();
  
 
-  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create a SideEffect
SideEffects are defined in SideEffect.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 11.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 3.0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Typed SideEffect
A typed SideEffect is a Java class that implements the MixinType it can be used on:
public abstract class MailNotifySideEffect extends SideEffectOf<Confirmable>
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Create a SideEffect
SideEffects are defined in SideEffect.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Bootstrap artifact:
TableÂ 11.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.bootstrap 0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
Typed SideEffect
A typed SideEffect is a Java class that implements the MixinType it can be used on:
public abstract class MailNotifySideEffect extends SideEffectOf<Confirmable>
     implements Confirmable
 {
     @Service

Modified: zest/site/content/java/develop/howto-leverage-properties.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-leverage-properties.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-leverage-properties.html (original)
+++ zest/site/content/java/develop/howto-leverage-properties.html Fri Apr 15 08:28:56 2016
@@ -68,7 +68,7 @@
 
   
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
Zestâ¢ in 2 hours
Depend on Zestâ¢ in your build
Assemble an Application
Transient Composites Tutorial

 Services Composites Tutorial
Use contextual fragments
Leverage Properties
Create a Constraint
Create a Concern
Create a SideEffect
Create an Entity
Configure a Service
Use @Invocation
Use I/O API
Zestâ¢ Build System
Writing Zestâ¢ Documentation
Releasing Zestâ¢
Leverage Properties
Zestâ¢ does not follow the JavaBeans standard for property support. Instead, a much more explicit concept is in place. The
 advantages are enormous, and the only real downside is that people are already destroyed, thinking in so called POJO
-terms.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core API artifact:
TableÂ 8.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.api 3.0-SNAPSHOT

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial 
 for details.
So in Zest, instead of writing;
public interface Book
+terms.
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core API artifact:
TableÂ 8.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.api 0

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for deta
 ils.
So in Zest, instead of writing;
public interface Book
 {
     String getTitle();
     String getAuthor();

Modified: zest/site/content/java/develop/howto-use-io.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/howto-use-io.html?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/howto-use-io.html (original)
+++ zest/site/content/java/develop/howto-use-io.html Fri Apr 15 08:28:56 2016
@@ -102,7 +102,7 @@ what the possible pieces could be:
1) is the client code that initiates a transfer, and which have to know the input and output source.
2) is the code that reads lines from an input.
3) is helper code that I use to keep track of whatâs going on, and which Iâd like to reuse no matter what kind of
 transfer is being done.
4) receives the data and writes it down. In this code, if I wanted to implement batching on the read and write side I
 could do so by changing the 2 and 4 parts to read/write multiple lines at a time.
The API
If you want to reproduce whatâs explained in this tutorial, remember to depend on the Core Runtime artifact that depends
-on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:
TableÂ 14.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.runtime 3.0-SNAPSHOT

See the Depend on Zestâ¢ in your build tutorial for details.
Once theses parts were identified it was mostly just a matter of putting interfac
 es on these pieces, and making sure
+on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:
TableÂ 14.Â Artifact
Group ID Artifact ID Version
org.apache.zest.core org.apache.zest.core.runtime 0

See the Depend on Zestâ¢ in your build tutorial for details.
Once theses parts were identified it was mostly just a matter of putting interfaces on th
 ese pieces, and making sure
 they can be easily used in many different situations. The result is as follows.
To start with we have Input:
public interface Input<T, SenderThrowableType extends Throwable>
 {
     <ReceiverThrowableType extends Throwable> void transferTo( Output<? super T, ReceiverThrowableType> output )

Modified: zest/site/content/java/develop/images/icons/admon/caution.svg
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/images/icons/admon/caution.svg?rev=1739254&r1=1739253&r2=1739254&view=diff
==============================================================================
--- zest/site/content/java/develop/images/icons/admon/caution.svg (original)
+++ zest/site/content/java/develop/images/icons/admon/caution.svg Fri Apr 15 08:28:56 2016
@@ -1,4 +1,24 @@
 
+
+