Qi4j and state modeling

SQL Support Sample

Note

This sample use PostgreSQL and drop all of its data once run in order to be runnable multiple times.
Sample of how to fully use Qi4j SQL support : SQL Library, SQL EntityStore and SQL Index/Query.
Here are the steps needed to setup the database using the psql utility command:
user@host $ psql postgres
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
DCI Sample
DCI Cargo Sample
Forum Sample
Car Rental Sample
SQL Support Sample
Swing Bindings Sample
SQL Support Sample
Note
This sample use PostgreSQL and drop all of its data once run in order to be runnable multiple times.
Sample of how to fully use Zestâ¢ SQL support : SQL Library,  SQL EntityStore and SQL Index/Query.
Browse Source
Here are the steps needed to setup the database using the psql utility command:
user@host $ psql postgres
 postgres=# CREATE USER jdbc_test_login WITH PASSWORD 'password';
 CREATE ROLE
 postgres=# CREATE DATABASE jdbc_test_db;

Modified: zest/site/content/java/develop/sample-swing.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/sample-swing.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/sample-swing.html (original)
+++ zest/site/content/java/develop/sample-swing.html Wed Jul  8 11:08:41 2015
@@ -66,7 +66,7 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Overview
DCI Sample
DCI Cargo Sample
Forum Sample
Car Rental Sample
SQL Support Sample
Swing Bindings Sample
Swing Bindings Sample
Sample of ho
 w to write custom binders.
Browse Source

+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
DCI Sample
DCI Cargo Sample
Forum Sample
Car Rental Sample
SQL Support Sample
Swing Bindings Sample
Swing Bindings Sample
Sample
  of how to write custom binders.
Browse Source

         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
         

             Apache Zest, Zest, Apache, the Apache feather logo, and the Apache Zest project logo are trademarks of The Apache Software Foundation.


Modified: zest/site/content/java/develop/samples.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/samples.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/samples.html (original)
+++ zest/site/content/java/develop/samples.html Wed Jul  8 11:08:41 2015
@@ -66,8 +66,8 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Overview
DCI Sample
DCI Cargo Sample
Forum Sample
Car Rental Sample
SQL Support Sample
Swing Bindings Sample
Samples
Overview
The Qi4j SDK comes with several sample applications. This is a very good place
-to look for code examples and recipes.
The samples are available in the samples/ directory of the Qi4j SDK.

+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
DCI Sample
DCI Cargo Sample
Forum Sample
Car Rental Sample
SQL Support Sample
Swing Bindings Sample
Samples
Overview
The Zestâ¢ SDK comes with several sample applications. This is a very good place
+to look for code examples and recipes.
The samples are available in the samples/ directory of the Zestâ¢ SDK.

         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
         

             Apache Zest, Zest, Apache, the Apache feather logo, and the Apache Zest project logo are trademarks of The Apache Software Foundation.


Modified: zest/site/content/java/develop/state-modeling.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/state-modeling.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/state-modeling.html (original)
+++ zest/site/content/java/develop/state-modeling.html Wed Jul  8 11:08:41 2015
@@ -1,5 +1,5 @@
 
-Qi4j and state modeling
+Zestâ¢ and state modeling
 
 
 
@@ -66,7 +66,7 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Highligts
Background
What is COP?
Whatâs an Object anyway?
Qi4j and state modeling
Related publications & projects
Qi4j and state modeling
(From Rickard Obergâs blog, http://www.jroller.com/rickard/entry/qi4j_and_state_modeling, 2009-02-19)
In the Qi4j project we strive to being able to express our domain as directly as possible, with as little translation
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Highligts
Background
What is COP?
Whatâs an Object anyway?
Zestâ¢ and state modeling
Related publications & projects
Zestâ¢ and state modeling
(From Rickard Obergâs blog, <
 a class="ulink" href="http://www.jroller.com/rickard/entry/qi4j_and_state_modeling" target="_top">http://www.jroller.com/rickard/entry/qi4j_and_state_modeling, 2009-02-19)
In the Zestâ¢ project we strive to being able to express our domain as directly as possible, with as little translation
 as possible between how we think about a domain and how it is actually coded.
 This then affects our entire view of how application frameworks should be constructed, and what we consider good and
 bad ways of implementing certain features.
One part which is a good example of this is persistent state modeling. In other approaches and frameworks one would
@@ -76,7 +76,7 @@ If POJOs are used for both Entities and
 in our heads when talking about them, always keeping mind what the POJO is doing in any particular context.
 In Domain Driven Design terms, POJOs are not in our Ubiquitous Language.
From a DDD perspective we want to talk about Entities and Values, Properties and Associations.
 If our code does not reflect this, then there is translation going on, and translation inevitably leads to information loss.
-In Qi4j, where Composites and not Objects, are the basic construct, we have created specialized forms to model these
+In Zestâ¢, where Composites and not Objects, are the basic construct, we have created specialized forms to model these
 concepts more explicitly.
 We have EntityComposites and ValueComposites, each with different ways of creating them and managing them.
 Both EntityComposites and ValueComposites can then have Properties, as first-class objects, but Properties in
@@ -119,7 +119,7 @@ their initial values be set to a default
 For Strings this is the empty string, for primitives they are what you would expect.
 For Collections they are set to empty collections of the type indicated.
 "@UseDefaults Property<List<String>> addresses();" would be initialized to an empty ArrayList, for example.
In addition I have set surName() to be @Optional.
-In Qi4j we have defined all properties to be not-null as the default, and the same goes for all parameters in method
+In Zestâ¢ we have defined all properties to be not-null as the default, and the same goes for all parameters in method
 invocations.
 If you explicitly want to allow properties to be null, so that for example "Madonna" would be an acceptable name,
 then you can mark it as @Optional.
@@ -151,7 +151,7 @@ and so functionality tend to not be put
 the Entity into a bunch of places.
 What should have been a neat and tidy little package is instead a anorectic little thing whose guts lay splashed
 around your code, looking all soggy and unappetizing.
What to do about this?
-One of the great inventions of Qi4j, I believe, is the notion of private mixins.
+One of the great inventions of Zestâ¢, I believe, is the notion of private mixins.
 That we can have mixins in an object which are explicitly HIDDEN from usage outside of it.
 How can we use this for state modeling?
 What youâd want to do is to model the state of an Entity as a private mixin, which is hidden from clients, and then
@@ -193,10 +193,10 @@ So you can make a UI widget for listing
 a PersonEntity or Nameable.
For extra credit you could move the construction of "fullName" into a method on the NameValue, so that the value is
 not only a dumb data container, but can also perform useful operations on itself.
 And for the performance aware, donât worry, the mixin is lazy-loaded, so if the particular usecase handling the
-Entity doesnât need the "Listable" interface the mixin will never be instantiated.
And so much moreâ¦
The above is just a small taste of what you can do with state modeling in Qi4j.
+Entity doesnât need the "Listable" interface the mixin will never be instantiated.
And so much moreâ¦
The above is just a small taste of what you can do with state modeling in Zestâ¢.
 There is also support for associations and many-associations, the notion of aggregates, and a complete pluggable
 system for persistence and indexing/querying of data.
-To end with, hereâs a sample of how some other state modeling concepts can be expressed in Qi4j:
interface PersonEntity
+To end with, hereâs a sample of how some other state modeling concepts can be expressed in Zestâ¢:
interface PersonEntity
         extends EntityComposite
 {
     Association<PersonEntity> father();
@@ -212,7 +212,7 @@ interface BookNoteEntity
     Association<BookEntity> book();
 }
 
-
I hope they are self-explanatory.
My hope is that with Composite Oriented Programming and Qi4j we can come one step closer to being able to express our
+
I hope they are self-explanatory.
My hope is that with Composite Oriented Programming and Zestâ¢ we can come one step closer to being able to express our
 domain as clearly as possible in code.

         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
         


Modified: zest/site/content/java/develop/ten-minutes-intro.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/ten-minutes-intro.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/ten-minutes-intro.html (original)
+++ zest/site/content/java/develop/ten-minutes-intro.html Wed Jul  8 11:08:41 2015
@@ -1,5 +1,5 @@
 
-Qi4j in 10 minutes
+Zestâ¢ in 10 minutes
 
 
 
@@ -66,15 +66,15 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Overview
Qi4j in 2 minutes
Qi4j in 10 minutes
Qi4j in 30 minutes
Qi4j in 2 hours
Depend on Qi4j 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
Build System
Writing Qi4j Documentation
Qi4j in 10 minutes
Tip
Theses tutorials are based on actual code found in the tutorials/ directory of the
-Qi4j SDK sources. You should start your favorite editor and find the code related to
+  
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
Build System
Writing Zestâ¢ Documentation
Zestâ¢ in 10 minutes
Tip
Theses tutorials are based on actual code found in the tutorials/ directory of the
+Zestâ¢ SDK sources. You should start your favorite editor and find the code related to
 this tutorial, run it and play with it.

-Qi4j does not introduce any new programming language, no additional compilers needed and all your existing tools
+Zestâ¢ does not introduce any new programming language, no additional compilers needed and all your existing tools
       work just like before. It is pure Java.
 

-Qi4j works with Composites.
+Zestâ¢ works with Composites.
 

-The equivalent of an Object instance in OOP, is a Composite instance in Qi4j.
+The equivalent of an Object instance in OOP, is a Composite instance in Zestâ¢.
 

 Composites are constructed from Fragments.
 

@@ -82,8 +82,8 @@ Fragments are Mixins, Concerns, Constrai
 

 Only Mixins carry Composite state. The others are shared between Composite instances.
 
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Â 2.Â Artifact
Group ID Artifact ID Version
org.qi4j.core org.qi4j.core.runtime 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.
See the Depend on Qi4j in your build tutorial for details.
Composition is done with Java interfaces and Annotations. Example;
@Concerns( { PurchaseLimitConcern.class, InventoryConcern.class } )
+on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:
TableÂ 2.Â Artifact
Group ID Artifact ID Version
org.qi4j.core org.qi4j.core.runtime 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.
See the Depend on Zestâ¢ in your build tutorial for details.
Composition is done with Java interfaces and Annotations. Example;
@Concerns( { PurchaseLimitConcern.class, InventoryConcern.class } )
 public interface OrderEntity
     extends Order, Confirmable,
             HasSequenceNumber, HasCustomer, HasLineItems,
@@ -118,10 +118,10 @@ methods that they declare, for instance;
 }
 
Extending the ConcernOf is a convenience mechanism, instead of an explicit @ConcernFor annotation on a private field,
 which can be used in rare occasions when you are not able to extend. This base class defines the next field, which is
-set up by the Qi4j runtime and points to the next fragment in the call stack.
We can also see that the InventoryService is provided to the concern, which is done with dependency injection. Qi4j
-also supports dependency injection via constructors and methods.
The above example is obviously doing persistence, and we have no code handling this. But Qi4j supports persistence
-directly in its Core, and it is taken care of by Qi4j, since it is declared as an EntityComposite.
-Nothing else is needed, provided that the Qi4j Runtime has been setup with one or more persisted EntityStores. But
+set up by the Zestâ¢ runtime and points to the next fragment in the call stack.
We can also see that the InventoryService is provided to the concern, which is done with dependency injection. Zestâ¢
+also supports dependency injection via constructors and methods.
The above example is obviously doing persistence, and we have no code handling this. But Zestâ¢ supports persistence
+directly in its Core, and it is taken care of by Zestâ¢, since it is declared as an EntityComposite.
+Nothing else is needed, provided that the Zestâ¢ Runtime has been setup with one or more persisted EntityStores. But
 we have a naming convention that EntityComposites have "Entity" as the suffix in its name.
There are other built-in Composite subtypes as well, such as ValueComposite and ServiceComposite. This distinction helps
 both to communicate intent as well as having more precisely defined functionality.
Now, letâs say that we want to send a mail to sales@mycompany.com when the order is confirmed. This is a SideEffect, and
 will execute after the Constraints, Concerns and Mixins. We add the SideEffect to the OrderEntity;
@SideEffects( MailNotifySideEffect.class )
@@ -161,9 +161,9 @@ public interface OrderEntity
         mailer.send( "sales@mycompany.com", builder.toString() );
     }
 }
-
The MailService is dependency injected, as we have seen before.
@This is telling Qi4j that the SideEffect needs a reference to the Composite instance that it belongs to.
By asking for both the HasCustomer and the HasLineItems types, we get type-safety and donât need to bother with casts.
-In fact, Qi4j will ensure that you canât even cast the hasCustomer instance to the HasLineItems type.
By not referencing the aggregated interface OrderEntity, we reduce the coupling of this SideEffect and it can be used
-in any other Composite where the HasCustomer and HasLineItems combination is used, for instance in an InvoiceEntity.
So, build the report, send it via the MailService.
Conclusion
In this short introduction, we have covered the essence of Qi4j. We have looked at what is a Composite, seen some of the
+
The MailService is dependency injected, as we have seen before.
@This is telling Zestâ¢ that the SideEffect needs a reference to the Composite instance that it belongs to.
By asking for both the HasCustomer and the HasLineItems types, we get type-safety and donât need to bother with casts.
+In fact, Zestâ¢ will ensure that you canât even cast the hasCustomer instance to the HasLineItems type.
By not referencing the aggregated interface OrderEntity, we reduce the coupling of this SideEffect and it can be used
+in any other Composite where the HasCustomer and HasLineItems combination is used, for instance in an InvoiceEntity.
So, build the report, send it via the MailService.
Conclusion
In this short introduction, we have covered the essence of Zestâ¢. We have looked at what is a Composite, seen some of the
 Fragments in action, and how simple it is to turn a Composite into a persisted Composite, known as an EntityComposite.

         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
         


Modified: zest/site/content/java/develop/thirty-minutes-intro.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/thirty-minutes-intro.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/thirty-minutes-intro.html (original)
+++ zest/site/content/java/develop/thirty-minutes-intro.html Wed Jul  8 11:08:41 2015
@@ -1,5 +1,5 @@
 
-Qi4j in 30 minutes
+Zestâ¢ in 30 minutes
 
 
 
@@ -66,12 +66,12 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Overview
Qi4j in 2 minutes
Qi4j in 10 minutes
Qi4j in 30 minutes
Qi4j in 2 hours
Depend on Qi4j 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
Build System
Writing Qi4j Documentation
Qi4j in 30 minutes
Tip
Theses tutorials are based on actual code found in the tutorials/ directory of the
-Qi4j SDK sources. You should start your favorite editor and find the code related to
-this tutorial, run it and play with it.
This introduction will deepen your understanding of Qi4j, as we touches on a couple of the common features of Qi4j. It
-is expected that you have gone through and understood the "Qi4j in 10 minutes" introduction.
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Â 3.Â Artifact
Group ID Artifact ID Version
org.qi4j.core org.qi4j.core.runtime 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.
See the Depend on Qi4j in your build tutorial for details.
We will go back to the OrderEntity example;
@Concerns( { PurchaseLimitConcern.class, InventoryConcern.class } )
+  
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
Build System
Writing Zestâ¢ Documentation
Zestâ¢ in 30 minutes
Tip
Theses tutorials are based on actual code found in the tutorials/ directory of the
+Zestâ¢ SDK sources. You should start your favorite editor and find the code related to
+this tutorial, run it and play with it.
This introduction will deepen your understanding of Zestâ¢, as we touches on a couple of the common features of Zestâ¢. It
+is expected that you have gone through and understood the "Zestâ¢ in 10 minutes" introduction.
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Â 3.Â Artifact
Group ID Artifact ID Version
org.qi4j.core org.qi4j.core.runtime 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.
See the Depend on Zestâ¢ in your build tutorial for details.
We will go back to the OrderEntity example;
@Concerns( { PurchaseLimitConcern.class, InventoryConcern.class } )
 public interface OrderEntity
     extends Order, Confirmable,
             HasSequenceNumber, HasCustomer, HasLineItems,
@@ -138,8 +138,8 @@ public class TrailableMixin<M>
         return instance;
     }
 }
-
Quite a lot of Qi4j features are leveraged above;
-[1] Property is a first class citizen in Qi4j, instead of getters/setters naming convention to declare properties.
+
Quite a lot of Zestâ¢ features are leveraged above;
+[1] Property is a first class citizen in Zestâ¢, instead of getters/setters naming convention to declare properties.
 [2] ValueComposite for Action means that it is among other things Immutable.
 [3] The Action extends a Property. We call that Property subtyping and highly recommended.
 [4] The CompositeBuilder creates Immutable Action instances.
We also need a Concern to hang into the methods of the Order interface.
public abstract class OrderAuditTrailConcern
@@ -205,7 +205,7 @@ the re-use value. It could look like thi
 }
 
The above construct is called a Generic Concern, since it implements java.lang.reflect.InvocationHandler instead of the
 interface of the domain model. The ConcernOf baseclass will also need to be of InvocationHandler type, and the
-Qi4j Runtime will handle the chaining between domain model style and this generic style of interceptor call chain.
Finally, we need to declare the Concern in the OrderEntity;
@Concerns({
+Zestâ¢ Runtime will handle the chaining between domain model style and this generic style of interceptor call chain.
Finally, we need to declare the Concern in the OrderEntity;
@Concerns({
         AuditTrailConcern.class,
         PurchaseLimitConcern.class,
         InventoryConcern.class
@@ -226,7 +226,7 @@ underlying store (provided the Runtime i
 the persistence concern of storage and retrieval. This enables many performance optimization opportunities as well as a
 more flexible Indexing strategy. The other thing to understand is that the Query API is using the domain model, in Java,
 and not some String based query language. We have made this choice to ensure refactoring safety. In rare cases, the
-Query API is not capable enough, in which case Qi4j still provides the ability to look up and execute native queries.
Letâs say that we want to find a particular Order from its SequenceNumber.
import static org.qi4j.api.query.QueryExpressions.eq;
+Query API is not capable enough, in which case Zestâ¢ still provides the ability to look up and execute native queries.
Letâs say that we want to find a particular Order from its SequenceNumber.
import static org.qi4j.api.query.QueryExpressions.eq;
 import static org.qi4j.api.query.QueryExpressions.gt;
 import static org.qi4j.api.query.QueryExpressions.templateFor;
 
@@ -294,10 +294,10 @@ for( HasCustomer hasCustomer : query )
 }
 
This covers the most basic Query capabilities and how to use it. For Querying to work, an Indexing subsystem must be
 assembled during bootstrap. At the time of this writing, only an RDF indexing subsystem exist, and is added most easily
-by assembly.addAssembler( new RdfNativeSesameStoreAssembler() ).
It can be a bit confusing to see Qi4j use Java itself as a Query language, but since we have practically killed the
+by assembly.addAssembler( new RdfNativeSesameStoreAssembler() ).
It can be a bit confusing to see Zestâ¢ use Java itself as a Query language, but since we have practically killed the
 classes and only operate with interfaces, it is possible to do a lot of seemingly magic stuff. Just keep in mind that
-it is pure Java, albeit heavy use of dynamic proxies to capture the intent of the query.
Conclusion
We have now explored a couple more intricate features of Qi4j, hopefully without being overwhelmed with details on how
-to create applications from scratch, how to structure applications, and how the entire Qi4j Extension system works.
+it is pure Java, albeit heavy use of dynamic proxies to capture the intent of the query.
Conclusion
We have now explored a couple more intricate features of Zestâ¢, hopefully without being overwhelmed with details on how
+to create applications from scratch, how to structure applications, and how the entire Zestâ¢ Extension system works.
 We have looked at how to add a Concern that uses a private Mixin, we have touched a bit on Generic Concerns, and
 finally a short introduction to the Query API.

         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.

Modified: zest/site/content/java/develop/tools-envisage.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/tools-envisage.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/tools-envisage.html (original)
+++ zest/site/content/java/develop/tools-envisage.html Wed Jul  8 11:08:41 2015
@@ -66,7 +66,7 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Overview
Envisage
Envisage
Envisage is a Swing based visualization tool for the Qi4j Application model.
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Envisage
Envisage
Envisage is a Swing based visualization tool for the Zestâ¢ Application model.
 Visualizations can be printed to PDFs.
Usage
Envisage can be easily used directly and prior your Application activation:
public static void main( String[] args )
     throws Exception
 {
@@ -79,7 +79,7 @@ Visualizations can be printed to PDFs.As you can see, Envisage operates on the ApplicationModel, this means that you
 can easily embedd it in your own Applications too.
Two gradle tasks runSample and runSchool are defined in this module as a
-shortcut to run the examples. See Build System.
Screenshots

 Embedd in your Application
TableÂ 78.Â Artifact
Group ID Artifact ID Version
org.qi4j.tool org.qi4j.tool.envisage 0


+shortcut to run the examples. See Build System.
Screenshots

 Embedd in your Application
TableÂ 78.Â Artifact
Group ID Artifact ID Version
org.qi4j.tool org.qi4j.tool.envisage 0


         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
         

             Apache Zest, Zest, Apache, the Apache feather logo, and the Apache Zest project logo are trademarks of The Apache Software Foundation.


Modified: zest/site/content/java/develop/tools.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/tools.html?rev=1689843&r1=1689842&r2=1689843&view=diff
==============================================================================
--- zest/site/content/java/develop/tools.html (original)
+++ zest/site/content/java/develop/tools.html Wed Jul  8 11:08:41 2015
@@ -66,9 +66,9 @@
   })();
  
 
-  
Qi4j
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glo
 ssaryÂ 
Overview
Envisage
Tools
Overview
The Qi4j SDK comes with usefull development tools. Theses tools can come in
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Envisage
Tools
Overview
The Zestâ¢ SDK comes with usefull development tools. Theses tools can come in
 handy when assembled into your Application in development
-Application Mode.
The tools are available in the tools/ directory of the Qi4j SDK.

+Application Mode.
The tools are available in the tools/ directory of the Zestâ¢ SDK.

         Copyright Â© 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
         

             Apache Zest, Zest, Apache, the Apache feather logo, and the Apache Zest project logo are trademarks of The Apache Software Foundation.
SQL Support Sample

Note

SQL Support Sample

Note

Swing Bindings Sample

Swing Bindings Sample

Samples

Overview

Samples

Overview

Qi4j and state modeling

Zestâ¢ and state modeling

Qi4j in 10 minutes

Tip

Zestâ¢ in 10 minutes

Tip

Conclusion

Conclusion

Qi4j in 30 minutes

Tip

Zestâ¢ in 30 minutes

Tip

Conclusion

Conclusion

Envisage

Envisage

Usage

Screenshots

Embedd in your Application

Screenshots

Embedd in your Application

Tools

Overview

Tools

Overview

Zestâ¢ and state modeling

Zestâ¢ in 10 minutes

Zestâ¢ in 30 minutes
