Depend on Zestâ¢ in your build

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 +

Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ

Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
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.qi4j.core	org.qi4j.core.bootstrap	2.1

Moreover, youâll need an EntityStore for persistence and an Indexing engine for querying. Choose 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.qi4j.core	org.qi4j.core.bootstrap	2.1

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. @@ -128,7 +128,7 @@ We must also assemble an EntityStore for ManufacturerEntity.class ); module.values( AccidentValue.class ); - [...snip...] + [...snip...] } } Modified: zest/site/content/java/2.1/howto-create-sideeffect.html URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/howto-create-sideeffect.html?rev=1704315&r1=1704314&r2=1704315&view=diff ============================================================================== --- zest/site/content/java/2.1/howto-create-sideeffect.html (original) +++ zest/site/content/java/2.1/howto-create-sideeffect.html Mon Sep 21 15:15:15 2015 @@ -66,7 +66,7 @@ })(); -

Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ

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.qi4j.core	org.qi4j.core.bootstrap	2.1

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
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
<
 tbody>Group ID Artifact ID Version
org.qi4j.core org.qi4j.core.bootstrap 2.1

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
@@ -131,7 +131,7 @@ arbitrary MixinType.
@Concerns( MyGenericSideEffect.class )
 public interface AnyMixinType
 {
-[...snip...]
+  [...snip...]
 
 }
 
Methods of the SideEffect Fragment will be called before the Mixin invocation.
AppliesTo
For generic SideEffects that should only trigger on methods with specific annotations or fulfilling some expression, add
@@ -140,7 +140,7 @@ implementation(s).
The SideEffect
 invocation. In other words the AppliesTo arguments are ORâed.
Here is how the declaration goes ;
@AppliesTo( { MyAnnotation.class, MyAppliesToFilter.class } )
 public class MyGenericSideEffect extends GenericSideEffect
 {
-[...snip...]
+  [...snip...]
 
 }
 
And how to use the annotation ;
@Concerns( MyGenericSideEffect.class )
@@ -153,7 +153,7 @@ public interface AnyMixinType
     void doSomethingElse();
 
 }
-[...snip...]
+  [...snip...]
 
 
Here only the doSomething() method will see the SideEffect applied whereas the doSomethingElse() method wonât.
Finally here is how to implement an AppliesToFilter:
public class MyAppliesToFilter implements AppliesToFilter
 {
@@ -163,7 +163,7 @@ public interface AnyMixinType
         return appliesTo;
     }
 
-    [...snip...]
+      [...snip...]
 
     private boolean evaluate( Method method )
     {

Modified: zest/site/content/java/2.1/howto-depend-on-zest.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/howto-depend-on-zest.html?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/howto-depend-on-zest.html (original)
+++ zest/site/content/java/2.1/howto-depend-on-zest.html Mon Sep 21 15:15:15 2015
@@ -1,5 +1,5 @@
 
-Depend on Zestâ¢ in your build
+Depend on Zestâ¢ in your build
 
 
 
@@ -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â¢
Depend on Zestâ¢ in your build
Note
Some of the Libraries and Extensions depend on artifacts that are not deployed in central, youâll need to
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
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â¢
Depend on Zestâ¢ in your build
Note
Some of the Libraries and Extensions depend on artifacts that are not deployed in central, youâll need to
 add other repositories to your build scripts accordingly.
Release artifacts, including sources and javadoc, are deployed to Maven Central:
http://repo1.maven.org/maven2/ (US)
http://uk.maven.org/maven2/ (Europe)
Snapshot artifacts, including sources and javadoc, are built against the develop branch and deployed weekly to the Apache SNAPSHOTS repository:
http://repository.apache.org/snapshots/
Manually
If you donât rely on your build scripts dependency resolution mechanism you should
 download the SDK distribution.
Using Maven
You simply declare dependencies on Zestâ¢ artifacts:
<dependencies>
     <dependency>

Modified: zest/site/content/java/2.1/howto-invocation-annotation.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/howto-invocation-annotation.html?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/howto-invocation-annotation.html (original)
+++ zest/site/content/java/2.1/howto-invocation-annotation.html Mon Sep 21 15:15:15 2015
@@ -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â¢
Use @Invocation
The @Invocation annotation is relatively unknown but can be rather powerful to use, especially when creating
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
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â¢
Use @Invocation
The @Invocation annotation is relatively unknown but can be rather powerful to use, especially when creating
 libraries that needs to be flexible of what the user needs to do.
@Invocation is a different InjectionScope, which is a concept to tell Zest runtime where to look for the
 instances to be injected. Other, more well-known, InjectionScope annotations are @This, @Structure and
 @Service.
The @Invocation injection scope can provide the following types, all related to the on-going method invocation,

Modified: zest/site/content/java/2.1/howto-leverage-properties.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/howto-leverage-properties.html?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/howto-leverage-properties.html (original)
+++ zest/site/content/java/2.1/howto-leverage-properties.html Mon Sep 21 15:15:15 2015
@@ -66,9 +66,9 @@
   })();
  
 
-  
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
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
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.qi4j.core org.qi4j.core.api 2.1

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
So i
 n 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.qi4j.core org.qi4j.core.api 2.1

At runtime you will need the Core Runtime artifact too. See the Depend on Zestâ¢ in your build tutorial for details.
So i
 n Zest, instead of writing;
public interface Book
 {
     String getTitle();
     String getAuthor();
@@ -99,7 +99,7 @@ Property still have a set() method, whic
 Metadata about each Property can be declared as MetaInfo.
 
@Structure
 Module module;
-[...snip...]
+  [...snip...]
 
     TransientBuilder<Book> builder = module.newTransientBuilder( Book.class );
     Book prototype = builder.prototype();
@@ -121,7 +121,7 @@ actual domain model. Such Swing client w
 }
 
Our generic Swing UI will be mainly reflective in nature, but when it gets hold of a Property, it can simply do;
    @Structure
     private Qi4j api;
-    [...snip...]
+      [...snip...]
 
     private void addProperty( JPanel panel, Property<?> property )
     {
@@ -129,7 +129,7 @@ actual domain model. Such Swing client w
         Icon icon = info.icon( SIZE_32_32 );
         panel.add(  new JLabel(info.displayName( this.locale ), icon, JLabel.CENTER) );
     }
-    [...snip...]
+      [...snip...]
 
 }
 


Modified: zest/site/content/java/2.1/howto-use-io.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/howto-use-io.html?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/howto-use-io.html (original)
+++ zest/site/content/java/2.1/howto-use-io.html Mon Sep 21 15:15:15 2015
@@ -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â¢
Use I/O API
Note
This article was written on Rickard Ãbergâs blog, 6 Nov 2010
The past week Iâve had to deal with a lot of data shuffling, both in raw form as bytes and strings, and as SPI and
+  
Zestâ¢
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
GlossaryÂ 
Overview
Zestâ¢ in 2 minutes
Zestâ¢ in 10 minutes
Zestâ¢ in 30 minutes
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â¢
Use I/O API
Note
This article was written on Rickard Ãbergâs blog, 6 Nov 2010
The past week Iâve had to deal with a lot of data shuffling, both in raw form as bytes and strings, and as SPI and
 domain level objects. What struck me is that it is notoriously hard to shuffle things from one place to another in a
 way that is scalable, performant and handles errors correctly. And I had to do some things over and over again, like
 reading strings from files.
So the thought occurred: there must be a general pattern to how this thing works, which can be extracted and put into a
@@ -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.qi4j.core org.qi4j.core.runtime 2.1

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 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.qi4j.core org.qi4j.core.runtime 2.1

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 these 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 )
@@ -116,7 +116,7 @@ throw SQLException and the output IOExce
 and receiver must know when either side screws up, so that they can recover properly and close any resources they have
 opened.
On the receiving side we then have Output:
public interface Output<T, ReceiverThrowableType extends Throwable>
 {
-[...snip...]
+  [...snip...]
 
     <SenderThrowableType extends Throwable> void receiveFrom( Sender<? extends T, SenderThrowableType> sender )
         throws ReceiverThrowableType, SenderThrowableType;
@@ -126,7 +126,7 @@ whatever resources it needs to write to,
 have the same type T, so that they agree on what is being sent. We will see later how this can be handled if this is
 not the case.
Next we have Sender:
public interface Sender<T, SenderThrowableType extends Throwable>
 {
-[...snip...]
+  [...snip...]
 
     <ReceiverThrowableType extends Throwable> void sendTo( Receiver<? super T, ReceiverThrowableType> receiver )
         throws ReceiverThrowableType, SenderThrowableType;
@@ -134,7 +134,7 @@ not the case.
Next we have Sender:
 
The Output invokes sendTo and passes in a Receiver that the Sender will use to send individual items. The sender at
 this point can start transferring data of type T to the receiver, one at a time. The Receiver looks like this:
public interface Receiver<T, ReceiverThrowableType extends Throwable>
 {
-[...snip...]
+  [...snip...]
 
     void receive( T item )
         throws ReceiverThrowableType;

Modified: zest/site/content/java/2.1/js/progressive-enhancement.js
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/js/progressive-enhancement.js?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/js/progressive-enhancement.js (original)
+++ zest/site/content/java/2.1/js/progressive-enhancement.js Mon Sep 21 15:15:15 2015
@@ -143,7 +143,7 @@ $( document ).ready( function($){
             case "Overview":
                 $dt.attr( "style", "margin-bottom: 24px" );
             // Tutorials
-            case "Zest\u2122 in 2 hours":
+            case "Zest\u2122 in 30 minutes":
             case "Leverage Properties":
             case "Use I/O API":
                 $dt.attr( "style", "margin-bottom: 24px" );

Modified: zest/site/content/java/2.1/lang-groovy.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/lang-groovy.html?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/lang-groovy.html (original)
+++ zest/site/content/java/2.1/lang-groovy.html Mon Sep 21 15:15:15 2015
@@ -66,7 +66,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
Scheduler
Servlet
Shiro Security
Shiro Web Security
Spring Integration
SQL
UID
UoWFile
Groovy Scripting
code
docs
tests
Groovy Scripting Library
TableÂ 22.Â Artifact
Group ID Artifact ID Version
org.qi4j.library org.qi4j.library.lang-groovy 2.1

The Groovy Scripting Library is a Generic mixin that implements interfaces by delegating to Groovy code from classpath resources.
But before looking at how to use the Scripting library weâll see t
 hat you donât need this library at all if you simply need to use Groovy classes as Fragments.
+  
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
Scheduler
Servlet
Shiro Security
Shiro Web Security
Spring Integration
SQL
UID
UoWFile
Groovy Scripting
code
docs
tests
Groovy Scripting Library
TableÂ 22.Â Artifact
Group ID Artifact ID Version
org.qi4j.library org.qi4j.library.lang-groovy 2.1

The Groovy Scripting Library is a Generic mixin that implements interfaces by delegating to Groovy code from classpath resources.
But before looking at how to use the Scripting library weâll see t
 hat you donât need this library at all if you simply need to use Groovy classes as Fragments.
 Then weâll see how to use Groovy class scripts and method scripts.
All examples below are based on this type:
public interface HelloSpeaker
 {
     String sayHello( String name );

Modified: zest/site/content/java/2.1/lang-javascript.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/2.1/lang-javascript.html?rev=1704315&r1=1704314&r2=1704315&view=diff
==============================================================================
--- zest/site/content/java/2.1/lang-javascript.html (original)
+++ zest/site/content/java/2.1/lang-javascript.html Mon Sep 21 15:15:15 2015
@@ -66,7 +66,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
Scheduler
Servlet
Shiro Security
Shiro Web Security
Spring Integration
SQL
UID
UoWFile
Javascript Scripting
code
docs
tests
The Javascript Scripting Library allows Mixin methods to be implemented in Javascript and loaded dynamically on first use.
TableÂ 23.Â Artifact
Group ID Artifact ID Version
org.qi4j.library org.qi4j.library.lang-javascript 2.1

The Javascript Scripting Library is a Generic mixin class that implements
+  
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
Scheduler
Servlet
Shiro Security
Shiro Web Security
Spring Integration
SQL
UID
UoWFile
Javascript Scripting
code
docs
tests
The Javascript Scripting Library allows Mixin methods to be implemented in Javascript and loaded dynamically on first use.
TableÂ 23.Â Artifact
Group ID Artifact ID Version
org.qi4j.library org.qi4j.library.lang-javascript 2.1

The Javascript Scripting Library is a Generic mixin class that implements
 Composite interfaces by delegating to JavaScript functions using Rhino. Each
 method in an interface is declared as a JS function in a file located in
 classpath with the name "<interface>.<method>.js", where the interface name

Create an Entity

Create an Entity

Basics First

Create a SideEffect

Typed SideEffect

Create a SideEffect

Typed SideEffect

AppliesTo

Depend on Zestâ¢ in your build

Note

Depend on Zestâ¢ in your build

Note

Manually

Using Maven

Use @Invocation

Use @Invocation

Leverage Properties

Leverage Properties

Use I/O API

Note

Use I/O API

Note

The API

Groovy Scripting

Groovy Scripting

Javascript Scripting

Javascript Scripting

Depend on Zestâ¢ in your build

Depend on Zestâ¢ in your build