1.1 --- a/json/src/main/java/net/java/html/json/package.html	Tue Jan 21 15:37:40 2014 +0100
     1.2 +++ b/json/src/main/java/net/java/html/json/package.html	Fri Jan 24 05:02:12 2014 +0100
     1.3 @@ -67,9 +67,17 @@
     1.4      You don't have bother with JavaScript. All your application logic is in
     1.5      Java. The necessary JavaScript needed for the HTML bindings remains hidden
     1.6      as an implementation detail of communication between the generated model
     1.7 -    class(es) and appropriate technology bridge (like artifact with id <code>ko-fx</code>
     1.8 -    and group id <code>org.netbeans.html</code>).
     1.9 +    class(es) and appropriate technology bridge. For example
    1.10 +    the <code>ko4j</code> module:
    1.11      </p>
    1.12 +    <pre>
    1.13 +&lt;dependency&gt;
    1.14 +  &lt;groupId&gt;org.netbeans.html&lt;/groupId&gt;
    1.15 +  &lt;artifactId&gt;ko4j&lt;/artifactId&gt;
    1.16 +  &lt;scope&gt;runtime&lt;/scope&gt;
    1.17 +&lt;/dependency&gt;
    1.18 +    </pre>
    1.19 +    
    1.20      <p>
    1.21      The model classes can be used for JSON based server communication. Just
    1.22      use <a href="OnReceive.html">@OnReceive</a> annotation to define a communication
    1.23 @@ -83,7 +91,7 @@
    1.24  &lt;dependency&gt;
    1.25    &lt;groupId&gt;org.glassfish.jersey.media&lt;/groupId&gt;
    1.26    &lt;artifactId&gt;html-json&lt;/artifactId&gt;
    1.27 -  &lt;version&gt;2.1&lt;/version&gt;
    1.28 +  &lt;version&gt;2.6&lt;/version&gt; &lt;-- or 2.6-SNAPSHOT until it gets released --&gt;
    1.29    &lt;scope&gt;runtime&lt;/scope&gt;
    1.30  &lt;/dependency&gt;
    1.31      </pre>