river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peter_firmst...@apache.org
Subject svn commit: r901152 [1/2] - /incubator/river/jtsk/trunk/doc/release-notes/
Date Wed, 20 Jan 2010 12:01:37 GMT
Author: peter_firmstone
Date: Wed Jan 20 12:01:35 2010
New Revision: 901152

URL: http://svn.apache.org/viewvc?rev=901152&view=rev
Log:
Release Notes for Apache River v2.1.2

Modified:
    incubator/river/jtsk/trunk/doc/release-notes/activate.html
    incubator/river/jtsk/trunk/doc/release-notes/browser.html
    incubator/river/jtsk/trunk/doc/release-notes/bugfixes.html
    incubator/river/jtsk/trunk/doc/release-notes/classdep.html
    incubator/river/jtsk/trunk/doc/release-notes/classserver.html
    incubator/river/jtsk/trunk/doc/release-notes/comsunjinithread.html
    incubator/river/jtsk/trunk/doc/release-notes/discovery.html
    incubator/river/jtsk/trunk/doc/release-notes/evseqnums.html
    incubator/river/jtsk/trunk/doc/release-notes/execpolicy.html
    incubator/river/jtsk/trunk/doc/release-notes/fiddler.html
    incubator/river/jtsk/trunk/doc/release-notes/index.html
    incubator/river/jtsk/trunk/doc/release-notes/jeri.html
    incubator/river/jtsk/trunk/doc/release-notes/join.html
    incubator/river/jtsk/trunk/doc/release-notes/lease.html
    incubator/river/jtsk/trunk/doc/release-notes/loader.html
    incubator/river/jtsk/trunk/doc/release-notes/mahalo.html
    incubator/river/jtsk/trunk/doc/release-notes/mercury.html
    incubator/river/jtsk/trunk/doc/release-notes/netjinientry.html
    incubator/river/jtsk/trunk/doc/release-notes/new.html
    incubator/river/jtsk/trunk/doc/release-notes/norm.html
    incubator/river/jtsk/trunk/doc/release-notes/outrigger.html
    incubator/river/jtsk/trunk/doc/release-notes/reggie.html
    incubator/river/jtsk/trunk/doc/release-notes/security.html
    incubator/river/jtsk/trunk/doc/release-notes/servicediscovery.html
    incubator/river/jtsk/trunk/doc/release-notes/servicestarter.html

Modified: incubator/river/jtsk/trunk/doc/release-notes/activate.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/activate.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/activate.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/activate.html Wed Jan 20 12:01:35 2010
@@ -25,7 +25,7 @@
 
 <center>
 <h1><code>net.jini.activation</code><br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
@@ -43,6 +43,40 @@
 
 </dl>
 
+<H3>Changes since the v2.0.1 release</H3>
+
+<dl>
+
+<dt><b>Disabled permission propagation</b></dt>
+<dd>
+<p><a href="../api/net/jini/activation/ActivatableInvocationHandler.html">
+<code>ActivatableInvocationHandler</code></a> by default no longer attempts
+to propagate dynamic permission grants from the dynamic proxy to the
+underlying activation identifier. If this functionality is required, it can
+be enabled by setting the
+<code>com.sun.jini.activation.enableActivateGrant</code> system property to
+<code>true</code>. If the
+<a href="../api/net/jini/activation/package-summary.html">
+<code>phoenix</code></a> activator has been configured
+to allow anonymous client activation requests, and the invocation
+constraints on the underlying activation identifier have been configured
+to allow anonymous activation calls, it is not necessary to enable this.
+That should be the preferred configuration. However, if the activator has
+been configured to use Kerberos authentication, then anonymous calls are
+not supported, and you will either have to enable the activate grant in
+clients and dynamically grant sufficient
+<a href="../api/net/jini/security/AuthenticationPermission.html">
+<code>AuthenticationPermission</code></a> and
+<a href="../api/net/jini/security/GrantPermission.html">
+<code>GrantPermission</code></a> to the proxy to permit activation calls
+to succeed, or else statically grant sufficient
+<code>AuthenticationPermission</code> to downloaded code in clients
+to permit activation calls to succeed.
+</dd>
+
+</dl>
+
+
 </ul>
 <hr>
 Licensed to the Apache Software Foundation (ASF) under one

Modified: incubator/river/jtsk/trunk/doc/release-notes/browser.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/browser.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/browser.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/browser.html Wed Jan 20 12:01:35 2010
@@ -25,7 +25,7 @@
 
 <center>
 <h1>Service Browser<br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
@@ -37,7 +37,40 @@
 <dl>
 <dt><b>None</b>
 </dl>
+
+
+<H3>Changes since the v2.0.1 release</H3>
+<dl>
+<dt><b>Service Starter support</b>
+<dd>The Service Browser can now be run as a nonactivatable entity under
+the Service Starter.
+<p>
+<dt><b>JAR File Changes</b>
+<dd>The codebase for the Service Browser should now contain two URLs, the
+first for <code>browser-dl.jar</code> and the second for
+<code>jsk-dl.jar</code>. The <code>Class-Path</code> manifest attribute
+for <code>browser.jar</code> now also includes <code>jsk-lib.jar</code>.
+<p>
+<dt><b>Security Policy File Changes</b>
+<dd>The security policy file for the Service Browser must now grant
+permissions to <code>jsk-lib.jar</code>.
+<p>
+<dt><b>Browsing JavaSpaces(TM) service entries</b>
+<dd>The Service Browser can now browse the entries of a JavaSpaces(TM)
+service that implements the
+<a href="../api/net/jini/space/JavaSpace05.html"><code>JavaSpace05</code></a>
+interface.
+<p>
+<dt><b>Configuration</b>
+<dd>A new <code>exitActionListener</code> configuration entry has been added,
+which can be used to set the action listener for the <b>Exit</b> item of the
+<b>File</b> menu. The new class,
+<a href="../api/com/sun/jini/example/browser/Browser.Exit.html"><code>Browser.Exit</code></a>,
+is a simple action listener that calls <code>System.exit</code>.
+</dl>
 </ul>
+
+
 <hr>
 Licensed to the Apache Software Foundation (ASF) under one
 or more contributor license agreements.  See the NOTICE file

Modified: incubator/river/jtsk/trunk/doc/release-notes/bugfixes.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/bugfixes.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/bugfixes.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/bugfixes.html Wed Jan 20 12:01:35 2010
@@ -18,13 +18,13 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html lang="en-US">
 <head>
-  <title>Apache River Release Notes, v2.1.1</title>
+  <title>Apache River Release Notes, v2.1.2</title>
 </head>
 <body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"
  link="#9b37cc" vlink="#cc1877" alink="#ffffff">
 <h1>
 <center> <a name="TOP">Apache River <br>
-</a><a href="index.html">v2.1.1 Release Notes</a></center>
+</a><a href="index.html">v2.1.2 Release Notes</a></center>
 </h1>
 <p>
 </p>

Modified: incubator/river/jtsk/trunk/doc/release-notes/classdep.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/classdep.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/classdep.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/classdep.html Wed Jan 20 12:01:35 2010
@@ -25,13 +25,40 @@
 
 <center>
 <h1><code>ClassDep</code><br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
 <H3>Description</H3>
 <code>ClassDep</code> is used to analyze a set of classes and determine on
 what other classes they directly or indirectly depend.
+<H3>Changes since the v2.1.1 release</H3>
+<dl>
+    The new implementation no longer depends upon the Java SDK <code>tools.jar</code>
+    library, <a href ="http://asm.ow2.org/">ASM</a> is now used to provide 
+    equivalent and extended functionality, including detecting dependencies
+    from Annotations and Generics.  Note that if a static class (nested class)
+    is included in the dependency graph, references from that static class to
+    its immediate lexically enclosing class are included in the dependency
+    search now by default.
+</dl>
+
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-7'>RIVER-7</a>] -         
+com.sun.jini.tool.ClassDep should be smarter with outer classes
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-8'>RIVER-8</a>] -         
+com.sun.jini.tool.ClassDep empty inside collection doesn't work
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-78'>RIVER-78</a>] -         
+ClassDep generates duplicate output lines
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-82'>RIVER-82</a>] -         
+ClassDep generates duplicate output lines
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-302'>RIVER-302</a>] -         
+ClassDep -newdirbehaviour option does not work
+</li>
+
 
 <H3>Changes since the v2.0.1 release</H3>
 <dl>

Modified: incubator/river/jtsk/trunk/doc/release-notes/classserver.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/classserver.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/classserver.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/classserver.html Wed Jan 20 12:01:35 2010
@@ -25,7 +25,7 @@
 
 <center>
 <h1><code>ClassServer</code><br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
@@ -37,6 +37,21 @@
 <dl>
 <dt><b>None</b></dt>
 </dl>
+<H3>Changes since the v2.0.1 release</H3>
+<dl>
+<dt><b>Multiple Directory Support</b>
+<dd>The class server can now serve up files from multiple directories.
+The <code>-dir</code> (or <code>-dirs</code>) command line option
+and the <code>dirlist</code> constructor parameter now accept a list
+of directories to serve files from, with entries separated by the
+system path-separator character.
+<p>
+<dt><b>Executable JAR file</b>
+<dd>There is a new executable JAR file, <code>classserver.jar</code>,
+that can be used to run the class server.
+</dl>
+
+
 </ul>
 <hr>
 Licensed to the Apache Software Foundation (ASF) under one

Modified: incubator/river/jtsk/trunk/doc/release-notes/comsunjinithread.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/comsunjinithread.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/comsunjinithread.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/comsunjinithread.html Wed Jan 20 12:01:35 2010
@@ -26,7 +26,7 @@
 <body text="black" bgcolor="white" link="#9b37cc" vlink="#cc1877" alink="white">
 <center>
 <h1><code>com.sun.jini.thread</code> package<br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <hr>
 <ul>
@@ -45,6 +45,71 @@
 <dt><b>None</b></dt>
 
 </dl>
+<H3>Changes since the v2.0.1 release</H3>
+
+A number of improvements have been made to the <a
+href="../api/com/sun/jini/thread/WakeupManager.html">
+<code>com.sun.jini.thread.WakeupManager</code></a>.
+<code>WakeupManager</code> instances are used to schedule tasks that need
+to be run in the future. Many of the services and utilities in the starter
+kit obtain the required <code>WakeupManager</code> instances from their
+configuration. <p>
+
+<dl>
+
+<dt><b>The <code>WakeupManager.ThreadDesc</code> Class Can Now Be More
+Usefully Subclassed and Has Been Made More Accessible</b>
+<dd>
+Instances of the <a href="../api/com/sun/jini/thread/WakeupManager.ThreadDesc.html"><code>
+<code>WakeupManager.ThreadDesc</code></a> class are used by
+<code>WakeupManager</code> to create threads. A <code>ThreadDesc</code>
+can be specified optionally when a <code>WakeupManager</code> is created,
+and/or when a task is scheduled that needs to be run in its own thread.
+The <a
+href="../api/com/sun/jini/thread/WakeupManager.ThreadDesc.html#thread(java.lang.Runnable)"><code>
+ThreadDesc.thread</code></a> method has been made public, which gives
+subclasses of <code>ThreadDesc</code> complete control over how threads are
+created and allows subclasses of  <code>WakeupManager</code> to invoke
+the <code> ThreadDesc.thread</code> method.
+Also, public <a
+href="../api/com/sun/jini/thread/WakeupManager.ThreadDesc.html#getGroup()"><code>getGroup</code></a>,
+<a
+href="../api/com/sun/jini/thread/WakeupManager.ThreadDesc.html#isDaemon()"><code>isDaemon</code></a>,
+and <a
+href="../api/com/sun/jini/thread/WakeupManager.ThreadDesc.html#getPriority()"><code>getPriority</code></a>
+methods have been added to <code>ThreadDesc</code> and the default
+implementation of <code>ThreadDesc.thread</code> has been changed to use
+them. This work had been assigned issue numbers 5091282 and 6308590.
+<p>
+
+<dt><b>Protected Factory Method for
+<code>WakeupManager.Ticket</code>s Has Been Added to <code>WakeupManager</code></b>
+<dd>
+
+When a task is added to a <code>WakeupManager</code>, the caller gets a <a
+href="../api/com/sun/jini/thread/WakeupManager.Ticket.html"><code>WakeupManager.Ticket</code></a>
+object than can be used to remove the task if necessary.  The protected
+method, <a
+href="../api/com/sun/jini/thread/WakeupManager.html#newTicket"><code>WakeupManager.newTicket</code></a>,
+has been added so subclasses of <code>WakeupManager</code> can create
+<code>Ticket</code> instances. This work had been assigned issue number
+6264220.
+<p>
+
+
+<dt><b><code>WakeupManager</code> Only Keeps Internal Thread Running When
+There Are Tasks Pending</b>
+<dd>
+
+Previous versions of <code>WakeupManager</code> always had one running
+(though often waiting) thread even if there were no pending tasks. This
+version of <code>WakeupManager</code> only creates its internal thread when
+the first task is enqueued. It will let this thread end, after a
+configurable timeout, if there are no tasks pending. This work had been
+assigned issue number 6190278.
+<p>
+
+</dl>
 
 <p>
 <hr>

Modified: incubator/river/jtsk/trunk/doc/release-notes/discovery.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/discovery.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/discovery.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/discovery.html Wed Jan 20 12:01:35 2010
@@ -21,16 +21,16 @@
       vlink="#cc1877" alink="#ffffff">
 
 
-<title>River Discovery Utilities Release Notes</title>
+<title>Jini Discovery Utilities Release Notes</title>
 
 <center>
-<h1>River Discovery Utilities<BR>
-v2.1.2 Release Notes</h1>
+<h1>Jini Discovery Utilities<BR>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
 <H3>Description</H3>
-The River discovery utilities contain
+The Jini discovery utilities contain
 a set of discovery management interfaces that define the policies to
 apply when implementing helper utilities that manage an entity's
 discovery duties: in particular, the management of multicast (group)
@@ -63,15 +63,86 @@
     <code>com.sun.jini.discovery</code></a>
   </ul>
 <p>
-The <i>River Discovery Utilities Specification</i> is available in
+The <i>Jini Discovery Utilities Specification</i> is available in
 <a href="../specs/html/discoveryutil-spec.html">html</a>.
 
 <p>
 <H3>Changes since the v2.1.1 release</H3>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-17'>RIVER-17</a>] -         
+Misleading logging message when discovery constraint checking is delayed
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-245'>RIVER-245</a>] -         
+Unicast discovery should close socket in case of connection exception.
+</li>
+  
+  <H3>Changes since the v2.0.1 release</H3>
 
 <dl>
-  <dt>None</dt>
-  </dl>
+  <dt> <b>API additions and changes</b>
+  <dd> Changes to the <a href="../api/net/jini/discovery/package-summary.html">
+       <code>net.jini.discovery</code></a> package.
+       <ul>
+       <li>Parsing of the input URL and host name arguments in the corresponding       <a href="../api/net/jini/discovery/ConstrainableLookupLocator.html">
+       <code>ConstrainableLookupLocator</code></a> and
+       <a href="../api/net/jini/core/discovery/LookupLocator.html">
+       <code>LookupLocator</code></a> constructors has been made stricter;
+       this may generate new <code>MalformedURLException</code>s. Note that
+       the implementation does not conform to the DJ 3.0 specification, which
+       requires parsing according to RFC 2396. The implementation is more
+       permissive and allows characters such as <code>'_'</code> in host names
+       to minimize backward incompatibility issues and anticipate compliance
+       with RFC 3986 (which obsoletes RFC 2396).
+       <li>
+       <code>ConstrainableLookupLocator</code> handles
+       <a href="../api/net/jini/core/constraint/ConnectionAbsoluteTime.html">
+       <code>ConnectionAbsoluteTime</code></a> and
+       <a href="../api/net/jini/core/constraint/ConnectionRelativeTime.html">
+       <code>ConnectionRelativeTime</code></a> constraints, enabling the
+       specification of timeouts on unicast discovery connection attempts.
+       <li>
+       <a href="../api/net/jini/discovery/LookupLocatorDiscovery.html">
+       <code>LookupLocatorDiscovery</code></a> handles any
+       <code>ConnectionRelativeTime</code> and <code>ConnectionAbsoluteTime</code>
+       constraints that may be set on the <code>LookupLocator</code>s passed into its
+       constructors.
+       <li>The
+       <a href="../api/net/jini/discovery/LookupDiscovery.html"> <code>LookupDiscovery</code></a>,
+       <code>LookupLocator</code>, <code>ConstrainableLookupLocator</code>, and
+       <code>LookupLocatorDiscovery</code> classes now try all the IP addresses
+       that a given host name may resolve to, instead of just the first one. This is as per the
+       recommendations in RFC 1123.
+       </ul>
+       <p>
+       Changes to the <a href="../api/com/sun/jini/discovery/package-summary.html">
+       <code>com.sun.jini.discovery</code></a> package.
+       <ul>
+       <li>
+       The <a href="../api/com/sun/jini/discovery/Discovery.html">
+       <code>Discovery</code></a> class now enables constraint checking to be optionally
+       delayed. With this change, constraint checks need not be performed as part of multicast
+       announcement or request decoding.
+       Discovery providers that support delayed constraint checking must implement the new
+       <a href="../api/com/sun/jini/discovery/MulticastAnnouncementDecoder.html">
+       <code>MulticastAnnouncementDecoder</code></a>
+       and <a href="../api/com/sun/jini/discovery/MulticastRequestDecoder.html">       <code>MulticastRequestDecoder</code></a> interfaces.
+       <li>
+       The <a href="../api/com/sun/jini/discovery/DiscoveryConstraints.html">
+       <code>DiscoveryConstraints</code></a> class supports processing of
+       <code>ConnectionRelativeTime</code> and <code>ConnectionAbsoluteTime</code>
+       constraints. Note that the processed constraints will no longer return
+       <code>ConnectionRelativeTime</code> and <code>ConnectionAbsoluteTime</code>
+       <code>ConnectionRelativeTime</code> and <code>ConnectionAbsoluteTime</code>
+       constraints. Note that the processed constraints will no longer return
+       <code>ConnectionRelativeTime</code> and <code>ConnectionAbsoluteTime</code>
+       as unfulfilled constraints.
+       </ul>
+       <p>
+
+  <dt> <b>Configuration</b>
+  <dd> The current implementation of the <code>LookupDiscovery</code>
+       utility now allows <code>ConnectionRelativeTime</code> and
+       <code>ConnectionAbsoluteTime</code> as part of its discovery constraints.
+ 
   
 <!-- No issues for now
 

Modified: incubator/river/jtsk/trunk/doc/release-notes/evseqnums.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/evseqnums.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/evseqnums.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/evseqnums.html Wed Jan 20 12:01:35 2010
@@ -26,7 +26,7 @@
 <body text="black" bgcolor="white" link="#9b37cc" vlink="#cc1877" alink="white">
 <center>
 <h1>Note on JavaSpaces Technology, Persistent Outrigger Services, and Event Sequence Numbers
-</code></h1>
+</h1>
 </center>
 <p>
 Previously the <i>JavaSpaces Service Specification</i> required that

Modified: incubator/river/jtsk/trunk/doc/release-notes/execpolicy.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/execpolicy.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/execpolicy.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/execpolicy.html Wed Jan 20 12:01:35 2010
@@ -24,7 +24,7 @@
 </H1>
  <ul>
 
-<p>Some River network technology-based services may be activatable and
+<p>Some Jini network technology-based services may be activatable and
 as such will require the use of an activation daemon.  The standard
 Java(TM) 2 Standard Edition (J2SE(TM)) Remote Method Invocation (Java RMI) activation daemon is
 <code>rmid</code>.  The Apache River release
@@ -284,11 +284,11 @@
      and
 
 <pre>     <a href="http://java.sun.com/j2se/1.4/docs/tooldocs/windows/rmid.html">http://java.sun.com/j2se/1.4/docs/tooldocs/windows/rmid.html</a>
-</pre></a>
+</pre>
 <P>
 <H3><a name="prev">
 How to achieve the behavior of <code>rmid</code> released in
-previous versions of the Java 2 SDK</H3></a>
+previous versions of the Java 2 SDK</a></H3>
 <P>
    The new security control can be effectively bypassed by assigning an
    exec policy that permits all commands and all options.  There is a
@@ -311,7 +311,7 @@
 <P>
 <H3><a name="assign">
 How to assign and maintain security controls
-</H3></a>
+</a></H3>
 <P>
    The default exec policy is used if the
    <CODE>sun.rmi.activation.execPolicy</CODE> system property is not
@@ -428,7 +428,7 @@
 <PRE>
   grant {
     permission com.sun.rmi.rmid.ExecOptionPermission
-	       "-Djava.security.policy=<b><var>configDir</b></var>/books.policy";
+	       "-Djava.security.policy=<var><b>configDir</b></var>/books.policy";
     permission com.sun.rmi.rmid.ExecOptionPermission
 	       "-Djava.rmi.server.codebase=*";
     permission com.sun.rmi.rmid.ExecOptionPermission

Modified: incubator/river/jtsk/trunk/doc/release-notes/fiddler.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/fiddler.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/fiddler.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/fiddler.html Wed Jan 20 12:01:35 2010
@@ -40,12 +40,140 @@
 and
 <a href="../api/net/jini/admin/Administrable.html"> <code>net.jini.admin.Administrable</code></a>.
 <p>
-
 <H3>Changes since the v2.1.1 release</H3>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-234'>RIVER-234</a>] -         
+(DOC) Fiddler manpage directions for HTTP server should reference 
+classserver.jar, not tools.jar
+</li>
+<H3>Changes since the v2.1 release</H3>
 <dl>
   <dt> <b>None</b></dt>
 </dl>
 
+<H3>Changes since the v2.0.1 release</H3>
+<dl>
+
+  <dt> <b>Configuration</b>
+  <dd> In this release, no new configuration entries have been added, nor have any other
+       changes occurred with respect to the configuration.
+       <p>
+       A full list of supported configuration entries is given in this service's
+       <a href="../api/com/sun/jini/fiddler/package-summary.html#fiddlerConfigEntries"> man page</a>.
+       <p>
+
+  <dt> <b>Logging</b>
+  <dd> In this release, no changes have occurred with respect to the logging mechanism
+       employed by Fiddler; which logs diagnostic information using a separate
+       <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/logging/Logger.html"> <code>Logger</code></a>
+       for each type of information logged. The name of each logger
+       is a dot-separated concatenation of the implementation package name,
+       <code>com.sun.jini.fiddler</code>, with a descriptive string. A description of each
+       logger used by this service, as well as what information is logged to which
+       logger, and at what logging level, is given in this service's
+       <a href="../api/com/sun/jini/fiddler/package-summary.html#fiddlerLoggers"> man page</a>.
+       <p>
+
+  <dt> <b>Bug Fixes of Interest</b>
+  <dd> A number of bugs have been addressed in this release of Fiddler.
+       What follows is a description of those bugs that might be of
+       interest:
+  <p>
+
+  <dt><b>4874580: FiddlerImpl throws NullPointerException in prepareNewLocators
+if locs is null</b><dt>
+  <dd> When calling the <code>register</code> method, if <code>null</code>
+       is passed as the value of the <code>locators</code> parameter,
+       a <code>NullPointerException</code> occurs.
+       <p>
+       This bug has been fixed.
+  </dd>
+  <p>
+  <dt><b>4979612: Fiddler relies on LookupLocator.equals to determine interest in discovered Regs</b><dt>
+  <dd> When Fiddler searches through its set of client registrations to
+       determine if any of those registrations are interested in a particular
+       previously discovered lookup service, it compares the locators of
+       interest from each registration to the locator that is returned by a call       to <code>getLocator</code> on the discovered lookup service. That
+       comparison is done using <code>LookupLocator.equals</code>.
+       <p>
+       <code>LookupLocator.equals</code> employs a case-insensitive string
+       compare of the host names of the locators to determine equality. Thus,
+       if one locator is associated with a hostname of "myHost",
+       and the other locator is associated with a fully qualified hostname like
+       "myHost.myCompany.com", <code>LookupLocator.equals</code> will return
+       <code>false</code>, and Fiddler will view as different, locators that
+       should actually be considered the same.
+       <p>
+       To address this bug, the implementation in this release now employs
+       the same strategy that <code>URL</code> currently employs. That is,
+       it first applies <code>LookupLocator.equals</code> (to do a case-insensitive
+       string compare). If the call to <code>LookupLocator.equals</code> returns       <code>false</code>, then the IP addresses associated with each locator
+       are retrieved and compared to determine equality.
+  </dd>
+  <p>
+  <dt><b>4984939: Fiddler threads should guard against lost interrupts</b><dt>
+  <dd> Thread subclasses in Fiddler that use logging and do not override the
+       <code>Thread.interrupt</code> method to set an "interrupted" field are
+       susceptible to lost interrupts. This is because <code>java.util.logging</code>
+       swallows internal <code>InterruptedIOException</code>s without setting
+       the receiving thread's interrupted status; effectively 'forgetting' the
+       interrupt that occurred. The end result is that some of Fiddler's threads       could endlessly loop instead of terminate, causing shutdown processing
+       in Fiddler to hang.
+       <p>
+       This bug has been fixed.
+  </dd>
+  <p>
+  <dt><b>5042473: FiddlerImpl.SetLocatorsTask handles NO_LOCATORS incorrectly</b><dt>
+  <dd> Prior to this release, when a client requested that locator discovery
+       be "turned off" by requesting the replacement of a registration's
+       locators-of-interest with the empty set (through an invocation of
+       the <code>setLocators</code> method), the result was the opposite
+       of what the specification prescribes. That is, the
+       locators-of-interest were <b>not</b> replaced at all.
+       <p>
+       This bug has been fixed.
+  </dd>
+  <p>
+  <dt><b>5049735: Fiddler should properly handle remote calls that arrive before init completes</b><dt>
+  <dd> Prior to this release, Fiddler contained no logic to ensure that
+       remote calls received before initialization completes would be handled
+       properly. Problems could occur, for example, if an instance of Fiddler is       run with a well-known endpoint that was used (and advertised) by a
+       previous instance of Fiddler.
+       <p>
+       To address this issue, Fiddler now handles such "early" calls by blocking       until initialization completes.
+  </dd>
+  <p>
+  <dt><b>6226306: Fiddler should allow null loginContext config entry, performing no JAAS login when null</b><dt>
+  <dd> Prior to this release, if Fiddler's configuration included a
+       <b><i>loginContext</i></b> entry, Fiddler would require that
+       entry to be non-<code>null</code>; throwing an exception if
+       a <code>null</code> value were entered. (Note that if the entry
+       were simply absent from the configuration, Fiddler interpretted
+       this as an indication that no JAAS login should be performed.)
+       <p>
+       To address this issue, Fiddler now interprets a <code>null</code>
+       value for the <i>loginContext</i> entry, as well as an absent
+       entry, as an indication that a JAAS login should not be performed.
+  </dd>
+  <p>
+  <dt> <b>Notes Of Interest</b>
+  <dd>
+       <p>
+       <b>Fiddler Has 3 Modes of Execution</b>
+       <p>
+       <ul>
+         <li> <i>Transient</i> - Fiddler does not persist its state and is not activatable
+         <li> <i>Nonactivatable</i> - Fiddler does persist its state but is not
+activatable
+         <li> <i>Activatable</i> - Fiddler persists its state and is activatable       </ul>
+       For details, see the
+       <a href="../api/com/sun/jini/fiddler/package-summary.html"> <code>com.sun.jini.fiddler</code></a>
+       package documentation.
+       <p>
+
+</dl>
+
+
+
 <!-- No issues for now
 <p>
 <H3>Known Issues (& Workarounds)</H3>

Modified: incubator/river/jtsk/trunk/doc/release-notes/index.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/index.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/index.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/index.html Wed Jan 20 12:01:35 2010
@@ -43,7 +43,7 @@
 secure, distributed systems which are adaptive to change.
 <hr>
 <h2>Notes of Interest for this Release</h2>
-This first release from the Apache River project is based on the
+This second release from the Apache River project is based on the
 contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
 and Service UI from Artima.  The release focuses on merging the
 two contributions together, structuring separate src and bin releases,
@@ -100,10 +100,288 @@
 to the <code>river-dev</code> list from the <a href="http://incubator.apache.org/river/mailing.html">
 project Mailing Lists</a> page.
 <hr>
-In this first release from the Apache River project, we're also including
-these release notes from the Jini Technology Starter Kit v2.0.2 release for 
-background and context: 
+    
+    <h2>Changes made since Apache River v2.1.1</h2>
+    <h2>        Bug
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-5'>RIVER-5</a>] - 
+HTTMPMD URLs can be considered equal while they are not
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-8'>RIVER-8</a>] -         
+com.sun.jini.tool.ClassDep empty inside collection doesn't work
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-17'>RIVER-17</a>] -         
+Misleading logging message when discovery constraint checking is delayed
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-18'>RIVER-18</a>] -         
+Order of discovery providers not maintained
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-22'>RIVER-22</a>] -         
+NPE in net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-24'>RIVER-24</a>] -         
+PreferredListGen can create illegal PREFERRED.LIST
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-78'>RIVER-78</a>] -         
+ClassDep generates duplicate output lines
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-82'>RIVER-82</a>] -         
+ClassDep generates duplicate output lines
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-91'>RIVER-91</a>] -         
+Uninstaller does not remove all items
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-205'>RIVER-205</a>] -         
+LookupDiscovery can give untrusted code access to privileged threads
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-209'>RIVER-209</a>] -         
+NullPointerException in SslConnection.checkConnectPermission()
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-212'>RIVER-212</a>] -         
+use of &quot;enum&quot; as a variable name
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-213'>RIVER-213</a>] -         
+(DOC) - JoinManger has typo in javadoc (missing &lt;/code&gt; termination tag)
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-215'>RIVER-215</a>] -         
+LookupDiscovery throws NullPointerException on terminate
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-216'>RIVER-216</a>] -         
+ConfigurationFile should throw ExceptionInInitializerError if unable to read 
+prohibited methods
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-217'>RIVER-217</a>] -         
+Browser incorrectly assumes event source is ServiceRegistrar proxy
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-223'>RIVER-223</a>] -         
+test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout fails on Linux
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-224'>RIVER-224</a>] -         
+Problem using browser to destroy service that supports DestroyAdmin but not 
+JoinAdmin
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-225'>RIVER-225</a>] -         
+NullPointerException in Reggie during destroy
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-227'>RIVER-227</a>] -         
+tools manpages command lines do not include line continuation characters
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-230'>RIVER-230</a>] -         
+(mux) SelectionManager catch Error block assumes getMessage() returns non-null
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-232'>RIVER-232</a>] -         
+JarWrapper and PreferredListGen uses jsk_install_dir and install_dir
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-234'>RIVER-234</a>] -         
+(DOC) Fiddler manpage directions for HTTP server should reference 
+classserver.jar, not tools.jar
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-240'>RIVER-240</a>] -         
+BasicInvocationDispatcher.dispatch could log more info for some exceptions
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-241'>RIVER-241</a>] -         
+Mercury spelling errore
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-242'>RIVER-242</a>] -         
+if a given ConnectionManager instance cannot create a reaper thread once, 
+it never will again
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-245'>RIVER-245</a>] -         
+Unicast discovery should close socket in case of connection exception.
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-252'>RIVER-252</a>] -         
+ComputeHttpmdCodebase NPE if resource bundle not found
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-253'>RIVER-253</a>] -         
+ComputeDigest NPE if resource bundle not found
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-254'>RIVER-254</a>] -         
+request initiation can block on I/O for inapplicable connection
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-255'>RIVER-255</a>] -         
+Outrigger DestroyThread does not catch exceptions from exporter.unexport
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-284'>RIVER-284</a>] -         
+[PATCH] fix bad ParticipantHandle.compareTo 
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-286'>RIVER-286</a>] -         
+[PATCH] iterators on synchronized collections still need synchronization
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-289'>RIVER-289</a>] -         
+Fix for RIVER-247 introduced wrong license headers and references
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-298'>RIVER-298</a>] -         
+No JavaDocs generated for package &quot;com.sun.jini.reliableLog&quot;
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-302'>RIVER-302</a>] -         
+ClassDep -newdirbehaviour option does not work
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-305'>RIVER-305</a>] -         
+qa/GetPermissions test still uses &quot;enum&quot; keyword
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-320'>RIVER-320</a>] -         
+Prebuilt hello example certificates have expired - need to provide new ones 
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-324'>RIVER-324</a>] -         
+Under certain circumstances, the ServiceDiscoveryManager internal LookupCache 
+implementation can incorrectly  process attribute change events before the 
+lookup snapshot is processed.
+</li>
+</ul>
+    
+<h2>        Improvement
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-7'>RIVER-7</a>] -         
+com.sun.jini.tool.ClassDep should be smarter with outer classes
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-9'>RIVER-9</a>] -         
+PreferredClassLoader should try to avoid making a direct check against the 
+first URL
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-25'>RIVER-25</a>] -         
+Improve logging for JoinManager at INFO and WARNING level
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-115'>RIVER-115</a>] -         
+Multiple jar files with conflicting lists need facilities to map the chosen 
+preferred value
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-116'>RIVER-116</a>] -         
+Multiple jar files with conflicting lists need facilities to map the chosen 
+preferred value
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-160'>RIVER-160</a>] -         
+add TrustEquivalence to browser's list of uninterestingInterfaces
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-201'>RIVER-201</a>] -         
+Show interfaces rather than classes in browser's Matching Services pane.
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-206'>RIVER-206</a>] -         
+Change default load factors from 3 to 1
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-210'>RIVER-210</a>] -         
+Browser should cancel event lease on exit
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-220'>RIVER-220</a>] -         
+LookupLocatorDiscovery catch Throwable blocks should also catch Throwable
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-226'>RIVER-226</a>] -         
+LLD: consider delaying the queuing of a discovery request immediately after a 
+discard
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-229'>RIVER-229</a>] -         
+reduce number of Reaper threads created by ConnectionManager
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-231'>RIVER-231</a>] -         
+ComputeHttpmdCodebase man page could be clarified with respect to algorithm used
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-233'>RIVER-233</a>] -         
+ComputeDigest instructions reference sha and sha1
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-243'>RIVER-243</a>] -         
+JarWrapper javadoc could be clearer wrt to classpath manifests
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-244'>RIVER-244</a>] -         
+Text area below menu bar in ServiceBrowser should not be editable
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-246'>RIVER-246</a>] -         
+Consider adding shutdown hook so Reggie sends final multicast packet if its VM 
+is terminated
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-247'>RIVER-247</a>] -         
+Destroy processing should use configurable duration and interval for unexporting
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-256'>RIVER-256</a>] -         
+Outrigger catch Throwable blocks should also catch Throwable
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-262'>RIVER-262</a>] -         
+ServiceUI Specification
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-270'>RIVER-270</a>] -         
+tar tasks in release* ant targets fail due to 100-char limitation and are 
+disabled
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-285'>RIVER-285</a>] -         
+LookupDiscoveryManager has unused variable declarations
+</li>
+</ul>
+    
+<h2>        New Feature
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-151'>RIVER-151</a>] -         
+ClassDep should have a method to determine if problems occurred
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-161'>RIVER-161</a>] -         
+Coalesce jars from multiple source dirs while retain current Manifest Classpath 
+semantics
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-163'>RIVER-163</a>] -         
+ClassDep doesn't pick up annotation or type parameter dependencies
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-292'>RIVER-292</a>] -         
+The service browser should provide support for the ServiceUI support
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-295'>RIVER-295</a>] -         
+Support configurable option to prevent from popup windows that require a 
+confirmation by the user
+</li>
+</ul>
+                
+<h2>        Task
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-294'>RIVER-294</a>] -         
+Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from the SVN 
+repository
+</li>
+</ul>
+            
+<h2>        Test
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-291'>RIVER-291</a>] -         
+Cannot build QA tests using the supplied make files
+</li>
+</ul>
+    <hr>
+    
+    <h2>Changes made since JTSK v2.1</h2>
+        
+<h2>        Bug
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-211'>RIVER-211</a>] -         
+source files for ServiceItem, ServiceMatches, and ServiceTemplate do not match 
+binary distribution
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-269'>RIVER-269</a>] -         
+build reports problem with javadoc generation on Windows
+</li>
+</ul>
+                        
+<h2>        Task
+</h2>
+<ul>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-263'>RIVER-263</a>] -         
+Remove outrigger logstore sources and build support
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-264'>RIVER-264</a>] -         
+integrate serviceui sources into jtsk trunk
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-266'>RIVER-266</a>] -         
+update build and source code for name, version number, ...
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-267'>RIVER-267</a>] -         
+Documentation update in release
+</li>
+</ul>
+<hr>
+                
+                <h2>Release notes from the Jini Technology Starter Kit v2.1</h2>
 <ul>
+        <li><a href=new.html>What's new in v2.1?</a>  
         <li><a href="bugfixes.html">Bugs fixed between v2.0.1 and v2.0.2 releases</a>
         <li><a href=#changes>Changes since the v2.0.1 release</a>
 	<li><a href=#platform>Platform dependencies</a>
@@ -120,7 +398,7 @@
 	<li><a href=#javadoc>Note on the API documentation</a>
 </ul>
 <a name="changes">
-<h2>Changes to the Starter Kit between v2.0.1 and v2.0.2</h2></a>
+<h2>Changes by Component, updated for v2.1.2</h2></a>
 <h3>Services</h3>
 <ul>
 	<li><a href="reggie.html">Reggie</a>

Modified: incubator/river/jtsk/trunk/doc/release-notes/jeri.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/jeri.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/jeri.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/jeri.html Wed Jan 20 12:01:35 2010
@@ -25,7 +25,7 @@
 
 <center>
 <h1><code>net.jini.jeri</code><br>
-v2.2.1 Release Notes</h1>
+Apache River v2.2.1 Release Notes</h1>
 </center>
 <HR>
 <UL>
@@ -37,12 +37,94 @@
 invocation (Jini ERI) and several Jini ERI transport layer providers.
 
 <H3>Changes since the v2.1.1 release</H3>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-22'>RIVER-22</a>] -         
+NPE in net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-209'>RIVER-209</a>] -         
+NullPointerException in SslConnection.checkConnectPermission()
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-212'>RIVER-212</a>] -         
+use of &quot;enum&quot; as a variable name
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-229'>RIVER-229</a>] -         
+reduce number of Reaper threads created by ConnectionManager
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-230'>RIVER-230</a>] -         
+(mux) SelectionManager catch Error block assumes getMessage() returns non-null
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-240'>RIVER-240</a>] -         
+BasicInvocationDispatcher.dispatch could log more info for some exceptions
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-254'>RIVER-254</a>] -         
+request initiation can block on I/O for inapplicable connection
+</li>
+
+<H3>Changes since the v2.0.1 release</H3>
 
-<dl>
 
-<dt><b>None</b></dt>
 
-</dl>
+<dt><b>Multihomed host support</b></dt>
+<dd>
+<p>As recommended by RFC 1123, the transport endpoints now attempt connections
+to all the IP addresses that a given host name may resolve to, instead of just
+the first one.
+</dd>
+
+<dt><b>Trust verification restriction</b>
+<dd><p><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html"><code>BasicJeriTrustVerifier</code></a>
+has been changed to trust fewer dynamic proxies. In particular, in addition to
+implementing
+<a href="../api/net/jini/core/constraint/RemoteMethodControl.html"><code>RemoteMethodControl</code></a>,
+the dynamic proxy must now implement one or more well-formed remote interfaces
+(ones that extend <code>Remote</code> and for which all methods declare
+<code>RemoteException</code> or a superclass in their throws clause), and
+must not implement any other interfaces except
+<a href="../api/net/jini/security/proxytrust/TrustEquivalence.html"><code>TrustEquivalence</code></a>.
+</dd>
+
+<dt><b>New <code>BasicJeriTrustVerifier</code> <code>protected</code>
+methods</b>
+
+<dd><p><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html"><code>BasicJeriTrustVerifier</code></a>
+has five new <code>protected</code> methods to allow for more
+convenient implementation of certain behaviors through subclassing:
+
+<ul>
+
+<li><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html#hasTrustedProxyClass(java.lang.Object,%20net.jini.security.TrustVerifier.Context)"><code>hasTrustedProxyClass</code></a>
+can be overridden by subclasses to control which dynamic proxy classes for
+Jini ERI proxies are considered locally trusted.
+
+<li><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html#hasTrustedClassLoader(java.lang.Object,%20net.jini.security.TrustVerifier.Context)"><code>hasTrustedClassLoader</code></a>
+can be overridden by subclasses to control the set of class loaders
+for which the class of a Jini ERI proxy, when defined by one of those
+loaders, is considered locally trusted.
+
+<li><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html#isTrustedProxyInterface(java.lang.Class,%20net.jini.security.TrustVerifier.Context)"><code>isTrustedProxyInterface</code></a>
+can be overridden by subclasses to control which dynamic proxy interfaces for
+Jini ERI proxies are considered locally trusted.
+
+<li><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html#isTrustedInvocationHandler(java.lang.reflect.InvocationHandler,%20net.jini.security.TrustVerifier.Context)"><code>isTrustedInvocationHandler</code></a>
+can be overridden by subclasses to support verification of invocation
+handlers that have a locally trusted class other than <a
+href="../api/net/jini/jeri/BasicInvocationHandler.html"><code>BasicInvocationHandler</code></a>
+(such as a subclass of <code>BasicInvocationHandler</code>).
+
+<li><a
+href="../api/net/jini/jeri/BasicJeriTrustVerifier.html#checkInvocationHandlerContent(net.jini.jeri.BasicInvocationHandler,%20net.jini.security.TrustVerifier.Context)"><code>checkInvocationHandlerContent</code></a>
+can be invoked by subclasses that override
+<code>isTrustedInvocationHandler</code> to perform the verification
+steps that the default implementation of
+<code>isTrustedInvocationHandler</code> would perform, except that the
+class of the invocation handler is not required to be
+<code>BasicInvocationHandler</code> exactly, so that trusted
+subclasses can be supported.
 
 </ul>
 <hr>

Modified: incubator/river/jtsk/trunk/doc/release-notes/join.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/join.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/join.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/join.html Wed Jan 20 12:01:35 2010
@@ -21,10 +21,10 @@
       vlink="#cc1877" alink="#ffffff">
 
 
-<title>River Join Utilities Release Notes</title>
+<title>Jini Join Utilities Release Notes</title>
 
-<center><h1>River Join Utilities
-  <BR>v2.1.2 Release Notes
+<center><h1>Jini Join Utilities
+  <BR>Apache River v2.1.2 Release Notes
 </h1></center>
 <HR>
 <UL>
@@ -33,27 +33,200 @@
 The class
 <a href="../api/net/jini/lookup/JoinManager.html"> <code>net.jini.lookup.JoinManager</code></a>
 is a utility class that, along with supporting interfaces and classes, 
-encapsulates functionality that can help River technology-enabled services 
-(<i>River services</i>) demonstrate good behavior in their discovery- 
-and registration-related interactions with River lookup services. 
+encapsulates functionality that can help Jini technology-enabled services 
+(<i>Jini services</i>) demonstrate good behavior in their discovery- 
+and registration-related interactions with Jini lookup services. 
 In particular, this utility performs functions related to lookup 
 service discovery and registration (<i>joining</i>), as well as lease
 renewal and attribute management.
 <p>
 The specification for the 
 <a href="../api/net/jini/lookup/JoinManager.html"> <code>JoinManager</code></a> 
-utility (join manager) is contained in the  <i>River Join Utilities Specification</i>,
+utility (join manager) is contained in the  <i>Jini Join Utilities Specification</i>,
 which is available in <a href="../specs/html/joinutil-spec.html">html</a>.
 <p>
 
 <H3>Changes since the v2.1.1 release</H3>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-25'>RIVER-25</a>] -         
+Improve logging for JoinManager at INFO and WARNING level
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-213'>RIVER-213</a>] -         
+(DOC) - JoinManger has typo in javadoc (missing &lt;/code&gt; termination tag)
+</li>
+
+<H3>Changes since the v2.0.1 release</H3>
 
 <dl>
-  <dt> <b>None</b>
-  </dt>  
+  <dt> <b>Configuration</b>
+  <dd> A new configuration entry has been added to the join manager implementation
+       in this release: <b>maxLeaseDuration</b>.
+       <p>
+       This new entry allows one to configure the maximum lease duration
+       (in milliseconds) that is requested from each discovered lookup service
+       on behalf of the service; both when the lease is initially requested,
+       as well as when renewal of that lease is requested. Thus, as this value
+       is made smaller, renewal requests will be made more frequently while the
+       service is up, and lease expiration will occur sooner when the service
+       goes down.
+       <p>
+       This new configuration entry is a result of <code>RFE 6202650</code>,
+       described <a href="#rfe6202650"> below</a>.
+       <p>
+       A full list of supported configuration entries is given in this utility's
+       <a href="../api/net/jini/lookup/JoinManager.html#jmConfigEntries"> class
+documentation</a>.
+       <p>
+
+  <dt> <b>Logging</b>
+  <dd> In this release, no changes have occurred with respect to the logging mechanism
+       employed by the join manager implementation; which logs diagnostic information to the
+       <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/logging/Logger.html"> <code>Logger</code></a>
+       named <code>net.jini.lookup.JoinManager</code>. For a description of the
+       information that is logged, as well as the associated logging levels, refer to the
+       <a href="../api/net/jini/lookup/JoinManager.html#jmLogging"> class documentation</a>.
+       <p>
+
+  <dt> <b>New Feature Enhancements</b>
+  <dd> In this release, the following feature enhancements have been added to
+       the join manager:
+  <p>
+  <dt><b>4879947: JoinManager should support changing the service proxy</b><dt>
+  <dd> The <a href="../api/net/jini/lookup/JoinManager.html"> public API</a> of
+the
+       join manager has been enhanced with a new method having two versions:
+
+<pre><code>public void replaceRegistration(Object serviceProxy) {...}
+public void replaceRegistration(Object serviceProxy, Entry[] attrSets) {...}</code></pre>
+
+       Using either version of this new method, one can register a new
+       reference to the service (optionally, with new attributes) which
+       was previously registered, by the join manager, with all discovered
+       lookup services. Refer to the <a href="../specs/html/joinutil-spec.html"> specification</a>
+       of the join manager for details on the semantics of this new method.
+       <p>
+       All necessary modifications were made to the join manager
+       implementation to comply with this change.
+  </dd>
+  <p>
+  <dt><b>5110241: JoinManager spec change - lease from discarded LUS should be cancelled, not removed (JU.5.1)</b><dt>
+  <dd> Section JU.5.1 of the join manager <a href="../specs/html/joinutil-spec.html"> specification</a>
+       states that when a lookup service has been discarded, the lease granted
+       by that lookup service should be removed -- but not cancelled -- from the       lease renewal manager, and the lease should be allowed to expire.
+       That section of the spec was changed to require that the lease
+       be ultimately cancelled rather than removed.
+       <p>
+       All necessary modifications were made to the join manager
+       implementation to comply with this change.
+  </dd>
+  <p>
+
+<a name="rfe6202650">
+  <dt><b>6202650: JoinManager should allow configurable control of lease renewal interval</b><dt>
+  <dd> When a service employs a join manager to manage the service's
+       join state, the join manager registers the service with
+       lookup services and then manages the leases associated with each
+       registration using a lease renewal manager. The lease renewal manager
+       used by the join manager is either created by the
+       join manager or supplied by the service itself.
+       <p>
+       After registering the service with a lookup service, the
+       join manager passes the resulting lease to the lease
+       renewal manager, requesting that the lease be renewed at regular
+       intervals based on the lease duration ultimately granted by the
+       lookup service. This means that when the service goes down and
+       the lease renewal manager is no longer available to renew the
+       service's lease, the lookup service will not notify interested
+       parties that the service is down until that lease duration has
+       actually passed. Thus, the timeliness of such notifications is
+       directly related to the maximum lease duration granted by the
+       particular lookup service implementation with which the service
+       was registered. If the developer of a system desires more timely
+       notification of a service's demise, the developer either has to
+       configure/administer the lookup service to grant shorter leases,
+       or subclass the lease renewal manager supplied to the
+       join manager.
+       <p>
+       Although the lease renewal manager provides the ability for the
+       user of the lease renewal manager to control the lease duration
+       requested, and thus the length of the renewal interval, until
+       now, the join manager did not provide the service
+       with access to this functionality. Over the years, a number of
+       users have asked for this capability. This feature enhancement
+       is intended to satisfy that request.
+       <p>
+       All necessary modifications were made to the join manager
+       implementation to comply with this change.
+  </dd>
+  <p>
+
+  <dt> <b>Bug Fixes of Interest</b>
+  <dd> A number of bugs have been addressed in this release of the
+       join manager. What follows is a description of those bugs that
+       might be of interest:
+  <p>
+
+  <dt><b>5090332: Specifying WakeupManager in JoinManager configuration causes thread leak</b><dt>
+  <dd> Specifying a wakeup manager in the join manager configuration causes
+       an extra thread to be created and never destroyed for every new
+       join manager that is created.
+       <p>
+       This bug has been fixed.
+  </dd>
+  <p>
+  <dt><b>5103210: JoinManager has race condition when a LUS is discarded/re-discovered</b><dt>
+  <dd> If a previously discovered lookup service is discarded from the discovery       manager being used by the join manager, there is a race condition
+       in the join manager that can result in the service not re-registering
+       with the lookup service when it is re-discovered. To understand how this
+       race can occur, consider the following sequence:
+<pre><code>discard lookup service --> DiscMgrListener.discarded()
+removeTasks
+queue DiscardProxyTask
+
+re-discover lookup service --> DiscMgrListener.discovered()
+if(!joinSet.contains(lookup service)) --> add lookup service to joinSet
+                                      --> queue RegisterTask
+DiscardProxyTask runs
+remove lookup service from joinSet
+cancel service's lease with the discarded lookup service</code></pre>
+
+       Because <code>DiscMgrListener.discovered()</code> tests <code>joinSet</code> for
+       the lookup service before <code>DiscardProxyTask</code> removes that lookup
+       service from <code>joinSet</code> (and cancels the service's lease with
+       the lookup service), the <code>RegisterTask</code> is not queued and run;       thus, the service is never re-registered with the lookup service.
+       <p>
+       This bug has been fixed.
+  </dd>
+  <p>
+  <dt><b>6181162: JoinManager should create default LDM only when no DiscoveryManagement is configured</b><dt>
+  <dd> Prior to interrogating the configuration for a
+       <a href="../api/net/jini/discovery/DiscoveryManagement.html"> <code>DiscoveryManagement</code></a>
+       item (entry name = <b><i>discoveryManager</i></b>), a default
+       <a href="../api/net/jini/discovery/LookupDiscoveryManager.html"> <code>LookupDiscoveryManager</code></a>
+       is first created. Although that manager is initialized to discover no groups and no locators,
+       the <a href="../api/net/jini/discovery/LookupDiscovery.html"> <code>LookupDiscovery</code></a>
+       instance used by the default discovery manager to perform group discovery creates
+       a thread to listen for and process multicast announcements, as well as
+       additional, related threads. Thus, if a deployer configures a <i>discoveryManagement</i>
+       item, the creation of the default lookup discovery manager -- and the threads
+       that manager ultimately creates -- is unnecessary, and wastes resources.
+       <p>
+       This bug has been fixed.
+  </dd>
+  <p>
+  <dt><b>6215208: JoinManager race - repeated UnknownLeaseException-Reregistration-UnknownLeaseException</b><dt>
+  <dd> A race condition was discovered in which an
+       <a href="../api/net/jini/core/lease/UnknownLeaseException.html"> <code>UnknownLeaseException</code></a>
+       followed by a re-registration can repeatedly occur. This condition is
+       intitiated by a discard of the lookup service coincident with a service
+       lease expiration.
+       <p>
+       This bug has been fixed.
+  </dd>
+
 
 </dl>
 
+
 <!-- No issues for now
 <p>
 <H3>Known Issues (& Workarounds)</H3>

Modified: incubator/river/jtsk/trunk/doc/release-notes/lease.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/lease.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/lease.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/lease.html Wed Jan 20 12:01:35 2010
@@ -24,8 +24,8 @@
 <title>River Lease Utilities Release Notes</title>
 
 <center>
-<h1>River Lease Utilities<BR>
-v2.1.2 Release Notes</h1>
+<h1>Jini<font size="-1"><sup>TM</sup></font> Lease Utilities<BR>
+River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
@@ -33,7 +33,7 @@
 The class <code>net.jini.lease.LeaseRenewalManager</code> is a utility
 class that provides for the systematic renewal and overall management of
 a set of leases associated with one or more remote entities on behalf of
-a local entity.  The <i>River Lease Utilities Specification</i> is
+a local entity.  The <i>Jini Lease Utilities Specification</i> is
 available in <a href="../specs/html/leaseutil-spec.html">html</a>.
 <p>
 
@@ -44,6 +44,48 @@
   <dt> <b>None</b></dt>
   
 </dl>
+<H3>Changes since the v2.0.1 release</H3>
+
+<dl>
+
+  <dt> <b>Configuration</b>
+  <dd> A new configuration entry named <code>roundTripTime</code> may
+       be used to set the worst-case latency to assume for a remote
+       call to renew a lease. This latency was previously hard-coded
+       to a value of ten seconds.
+       A full list of supported configuration entries is given in the
+       <code>LeaseRenewalManager</code> <a
+       href="../api/net/jini/lease/LeaseRenewalManager.html#configEntries">
+       class documentation</a>. <p>
+
+  <dt> <b>Logging</b>
+  <dd> In this release, no changes have occurred with respect to the logging mechanism
+       employed by the <code>LeaseRenewalManager</code>, which logs
+       diagnostic information to the <a
+       href="http://java.sun.com/j2se/1.4/docs/api/java/util/logging/Logger.html">
+       <code>Logger</code></a> named
+       <code>net.jini.lease.LeaseRenewalManager</code>. A description of
+       what information is logged at what logging levels is given in the
+       <a
+       href="../api/net/jini/lease/LeaseRenewalManager.html#logging">
+       class documentation</a>.
+  <p>
+  <dt> <b>Bug Fixes of Interest</b>
+
+  <dd> A number of bugs have been addressed in this release of the
+       <code>LeaseRenewalManager.</code> What follows is a description of those
+       bugs that might be of interest:
+  <p>
+
+  <dt><b>5015237: <code>LeaseRenewalManager</code> does not log lease
+         renewal failures if no listener is specified</b><dt>
+
+  <dd>The renewal failure logging code had an unnecessary dependency
+      on the existence of a registered listener.
+      <p>
+      This bug has been fixed.
+  </dd>
+</dl>
 
 <!-- No issues for now
 

Modified: incubator/river/jtsk/trunk/doc/release-notes/loader.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/loader.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/loader.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/loader.html Wed Jan 20 12:01:35 2010
@@ -25,7 +25,7 @@
 
 <center>
 <h1><code>net.jini.loader</code><br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <HR>
 <UL>
@@ -38,12 +38,60 @@
 
 <H3>Changes since the v2.1.1 release</H3>
 
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-9'>RIVER-9</a>] -         
+PreferredClassLoader should try to avoid making a direct check against the 
+first URL
+</li>
+
+<H3>Changes since the v2.0.1 release</H3>
+
 <dl>
 
-<dt><b>None</b></dt>
+<dt><b><code>PreferredClassProvider</code> constructors now require a
+permission</b>
+
+<dd><p>The constructors of <a
+href="../api/net/jini/loader/pref/PreferredClassProvider.html"><code>PreferredClassProvider</code></a>
+now check that the current security context has the permission
+<code>RuntimePermission("createClassLoader")</code>, and they throw a
+<code>SecurityException</code> if that check fails.  The primary
+consequence of this change is that the protection domain of a subclass
+of <code>PreferredClassProvider</code> must have this permission in
+order for the subclass to be instantiated.  Instances of
+<code>PreferredClassProvider</code> are typically only instantiated as
+part of the internal process of looking up and initializing the
+<code>RMIClassLoader</code> provider, so this change is unlikely to
+affect the permission requirements of classes other than
+<code>PreferredClassProvider</code> subclasses.
+
+<dt><b>New <code>PreferredClassLoader</code> constructor with
+<code>URLStreamHandlerFactory</code> parameter</b>
+
+<dd><p><a
+href="../api/net/jini/loader/pref/PreferredClassLoader.html"><code>PreferredClassLoader</code></a>
+has a <a
+href="../api/net/jini/loader/pref/PreferredClassLoader.html#PreferredClassLoader(java.net.URL[],%20java.lang.ClassLoader,%20java.lang.String,%20boolean,%20java.net.URLStreamHandlerFactory)">new
+constructor</a>, with a <code>URLStreamHandlerFactory</code> parameter
+that can be used to control the <code>URLStreamHandler</code> used
+when the loader creates new <code>URL</code> objects (which it does in
+order to load classes and resources from JAR files, by using the
+<code>"jar"</code> URL scheme).  This new constructor is intended to
+parallel the superclass <code>java.net.URLClassLoader</code>
+constructor that has a <code>URLStreamHandlerFactory</code> parameter.
+
+<dt><b>New <code>PreferredClassProvider</code> <code>protected</code>
+method <code>createClassLoader</code></b>
+
+<dd><p><a
+href="../api/net/jini/loader/pref/PreferredClassProvider.html"><code>PreferredClassProvider</code></a>
+has a new <code>protected</code> method, <a
+href="../api/net/jini/loader/pref/PreferredClassProvider.html#createClassLoader(java.net.URL[],%20java.lang.ClassLoader,%20boolean)"><code>createClassLoader</code></a>,
+which can be overridden by subclasses to customize the creation of new
+class loaders created by the provider.
 
 </dl>
 
+
 <H3>Known Issues (& Workarounds)</H3>
 
 <dl>

Modified: incubator/river/jtsk/trunk/doc/release-notes/mahalo.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/mahalo.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/mahalo.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/mahalo.html Wed Jan 20 12:01:35 2010
@@ -37,12 +37,84 @@
 <p>
 
 <H3>Changes since the v2.1.1 release</H3>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-284'>RIVER-284</a>] -         
+[PATCH] fix bad ParticipantHandle.compareTo 
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-286'>RIVER-286</a>] -         
+[PATCH] iterators on synchronized collections still need synchronization
+</li>
+
+<H3>Changes since the v2.1 release</H3>
 <dl>
 
   <dt> <b>None</b></dt>
   
        
 </dl>
+
+<H3>Changes since the v2.0.1 release</H3>
+<dl>
+
+  <dt> <b>Configuration</b></dt>
+  <dd> The following configuration entries have been added to the
+       Mahalo implementation:
+       <UL>
+       <LI> <B>settlerPool</B> -  The pool of threads used to settle outstanding
+            transactions.
+       <LI> <B>taskPool</B> -  The pool of threads used to settle transactions.
+       </UL>
+       These "thread pool" objects can now be sized for end user
+       applications. See Mahalo's package
+       <a href="../api/com/sun/jini/mahalo/package-summary.html#configuration">documentation</a>
+       for more detail.
+  </dd>
+  <dt> <b>Bug Fixes of Interest</b></dt>
+  <dd> The following bugs have been addressed in this release:
+  <p>
+  <dl>
+  <dt><b>
+      4285733: Is the Transaction spec correct about permissible votes?
+      </b></dt>
+  <dd>Section TX.2.7 of the
+      Jini (TM) Transaction Specification was changed to correct the permissible     
+      vote outcomes for <code>prepare</code>. Specifically, the
+      <code>COMMITTED</code> vote was changed to <code>PREPARED</code>.
+  </dd>
+  <dt><b>
+      4394196: Txn specs fixes
+      </b></dt>
+  <dd>Section TX.1.3 of the
+      Jini (TM) Transaction Specification was changed to emphasize that Java(TM)      
+      Remote Method Invocation (Java RMI) semantics are replied upon and not any particular
+      implementation. Section TX.2.3 removed a confusing "crash count" example.
+      In section TX.2.7, the paragraphs dealing with <code>abort</code>
+      and <code>prepareAndCommit</code> were modified for clarity. Section 2.8
+      was modified to note that the commit point record can be removed after
+      successfully returning from <code>abort</code>
+      (in addition to <code>commit</code>). Section 2.8.1 added an additional
+      bullet item noting that <code>getState</code> can return
+      <code>ABORTED</code>.
+  </dd>
+  <dt><b>
+      4761012: prepareAndCommit semantics amibiguous wrt idempotentcy
+      </b></dt>
+  <dd>Section TX.2.6 & TX.2.7 of the
+      Jini (TM) Transaction Specification were changed to note that
+      <code>prepareAndCommit</code> calls may not be idempotent.
+  </dd>
+  <dt><b>
+      5054742: Transaction spec does not specify whether or not participant
+      commit is atomic
+      </b></dt>
+  <dd>Section TX.3.5 of the
+      Jini (TM) Transaction Specification was changed to note that
+      participants are not required to implement atomic <code>abort</code> and
+      <code>commit</code> calls.
+  </dd>  </dl>
+  <p>
+
+</dl>
+
 <!-- N/A 
 <p>
 <H3>Known Issues (& Workarounds)</H3>

Modified: incubator/river/jtsk/trunk/doc/release-notes/mercury.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/mercury.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/mercury.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/mercury.html Wed Jan 20 12:01:35 2010
@@ -38,12 +38,42 @@
 <p>
 
 <H3>Changes since the v2.1.1 release</H3>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-241'>RIVER-241</a>] -         
+Mercury spelling errore
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-247'>RIVER-247</a>] -         
+Destroy processing should use configurable duration and interval for unexporting
+</li>
+<li>[<a href='https://issues.apache.org/jira/browse/RIVER-289'>RIVER-289</a>] -         
+Fix for RIVER-247 introduced wrong license headers and references
+</li>
+
+<H3>Changes since the v2.1 release</H3>
+<dl>None</dl>
+
+<H3>Changes since the v2.0.1 release</H3>
 
 <dl>
 
-  <dt> <b>None</b></dt>
-  
+  <dt> <b>"Pull" Functionality</b>
+  <dd> The Jini(TM) Event Mailbox Service
+       <a href="../specs/html/mailbox-spec.html">Specification</a>
+       was augmented with additional classes and
+       interfaces that provide synchronous access to
+       events (see sections EM.5-EM.7). Mercury was also
+       updated to implement this new functionality. <BR>
+       The following work still needs to be done:
+       <UL>
+       <LI>Implement the timeout functionality for
+           <code>RemoteEventIterator.next</code>
+       <LI>Make the batching implementation configurable. For example,
+           configuring the number of events that get returned to the
+           event mailbox client in a single call. Currently all the available
+           events are sent.
+       </UL>
+       <p>
 </dl>
+
        
 <!-- No issues for now
 
@@ -53,6 +83,7 @@
 
 -->
 
+
 </ul>
 <hr>
 Licensed to the Apache Software Foundation (ASF) under one

Modified: incubator/river/jtsk/trunk/doc/release-notes/netjinientry.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/netjinientry.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/netjinientry.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/netjinientry.html Wed Jan 20 12:01:35 2010
@@ -26,7 +26,7 @@
 <body text="black" bgcolor="white" link="#9b37cc" vlink="#cc1877" alink="white">
 <center>
 <h1><code>net.jini.entry</code> package<br>
-v2.1.2 Release Notes</h1>
+Apache River v2.1.2 Release Notes</h1>
 </center>
 <hr>
 <ul>
@@ -47,7 +47,59 @@
 
 </dl>
 
+<H3>Changes since the v2.0.1 release</H3>
+
+<dl>
+
+<dt><b>The API Documentation is Now the Formal Specification</b>
+<dd>
+
+Previously, the formal specification for the <code>net.jini.entry</code>
+package was a separate document. With this release, the formal specification
+is the revised API Documentation. As part of this change the specification
+language was generally cleaned up and made tighter.<p>
+
+<dt><b>Behavior of Various <code>AbstractEntry</code> Methods Clarified</b>
+<dd>
+
+The previous versions of the specification for <code><a
+href="../api/net/jini/entry/AbstractEntry.html">net.jini.entry.AbstractEntry</a></code>
+did not specify how the static <code>equals</code>, <code>hashCode</code>,
+and <code>toString</code> methods behaved if passed <code>null</code>
+values. This version of the specification specifies that :
+
+<ul>
+<li> <code>equals</code> should return <code>true</code> if both
+     arguments are <code>null</code>, and <code>false</code> if
+     only one argument is <code>null</code>.
+<li> <code>hashCode</code> should return <code>0</code> if passed
+     <code>null</code>.
+<li> <code>toString</code> should return <code>"null"</code> if
+     passed <code>null</code>.
+</ul>
 <p>
+Note: Previously our implementation of <code>AbstractEntry</code> would
+throw a <code>NullPointerException</code> if any of these methods were
+passed a <code>null</code> value.
+<p>
+
+Also, the specification of the static <code>toString</code> method was
+changed to require that the returned string include the name of the
+argument's class.
+
+<dt><b> <code>UnusableEntriesException</code> Added</b>
+<dd>
+
+The <code><a
+href="../api/net/jini/entry/UnusableEntriesException.html">net.jini.entry.UnusableEntriesException</a></code>
+class was added. <code>UnusableEntriesException</code> can be used by
+methods that normally return a collection of entries when one or more of
+the entries can't be unmarshalled.
+
+</dl>
+
+<p>
+
 <hr>
 Licensed to the Apache Software Foundation (ASF) under one
 or more contributor license agreements.  See the NOTICE file

Modified: incubator/river/jtsk/trunk/doc/release-notes/new.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/new.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/new.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/new.html Wed Jan 20 12:01:35 2010
@@ -24,35 +24,17 @@
  style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
 <h1>
 <center> <a name="TOP">Apache River  <br>
-</a><a href="index.html">v2.1.1 Release Notes</a></center>
+</a><a href="index.html">v2.1.2 Release Notes</a></center>
 </h1>
 <p>
 </p>
 <hr>
 <ul>
-  <h2>What's new in v2.1.1</h2>
+  <h2>Release notes from v2.1</h2>
   <p> </p>
   <dl>
 
-  
-    <dt><b><p>
-Installer</b> </dt>
-    <dd>The Porter release includes an installer created with InstallAnywhere(TM) 
-    by Zero G Software. Installers are provided for Windows, Linux, the Solaris(TM)
-     Operating System, MacOS X, and any other Java(TM) technology enabled platform. The installer includes an environment verification option that:
-      <ul>
-        <li>Verifies that multicast is enabled </li>
-        <li>Verifies that the host IP address is not a loopback address</li>
-        <li>Checks for multiple network interfaces</li>
-        <li>Launches the contributed services and a service browser</li>
-        <li>Warns if any of these steps produce unexpected results</li>
-      </ul>
-  <p>
-    The installer creates a single platform-dependent executable for
-    starting the browser and services. This executable is available after
-    installation in the top level "installverify" directory. In addition,
-    an uninstaller will be created in the top level "uninstall" directory.<br>
-    </dd>
+<p>Note that some of the links here contain updated information since v2.1</p>
     <dt><b><p>
 Ant build support</b> </dt>
     <dd>This release contains support for generating binary
@@ -68,16 +50,7 @@
       </ul>
     </dd>
     <dt><b><p>
-Licensing change</b> </dt>
-    <dd>Beginning with the v2.1Beta release, Sun is transitioning 
-    to the use of the Apache License, v2.0 for this technology.<p>
-      <b>More Information</b>
-      <ul>
-        <li><a href="http://www.apache.org/licenses/LICENSE-2.0.txt">
-        Apache License, v2.0</a></li>
-      </ul>
-    </dd>
-    <dt><b><p><code>
+<code>
 EnvCheck</code> tool</b> </dt>
     <dd>This new tool is used to perform validity checks on the runtime
     environment of a client or service by validating the system properties
@@ -216,8 +189,6 @@
       </ul>
     </dd>
     </ul>
-  </dl>
-</ul>
 
 <hr>
 Licensed to the Apache Software Foundation (ASF) under one

Modified: incubator/river/jtsk/trunk/doc/release-notes/norm.html
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/doc/release-notes/norm.html?rev=901152&r1=901151&r2=901152&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/doc/release-notes/norm.html (original)
+++ incubator/river/jtsk/trunk/doc/release-notes/norm.html Wed Jan 20 12:01:35 2010
@@ -47,6 +47,50 @@
 <dl>
   <dt> <b>None</b>
 </dl>
+<H3>Changes since the v2.0.1 release</H3>
+
+<dl>
+
+  <dt> <b>Configuration</b>
+  <dd> In this release, no new configuration entries have been added, nor have any other
+       changes occurred with respect to the configuration.
+       <p>
+       A full list of supported configuration entries is given in this service's
+       <a href="../api/com/sun/jini/norm/package-summary.html#configuration"> man page</a>.
+       <p>
+
+  <dt> <b>Logging</b>
+  <dd> In this release, no changes have occurred with respect to the logging mechanism
+       employed by Norm, which logs diagnostic information using a separate
+       <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/logging/Logger.html"> <code>Logger</code></a>
+       for each type of information logged. The name of each logger
+       is a dot-separated concatenation of the implementation package name,
+       <code>com.sun.jini.norm</code>, with a descriptive string. A description
+of each
+       logger used by this service, as well as what information is logged to which
+       logger, and at what logging level, is given in this service's
+       <a href="../api/com/sun/jini/norm/package-summary.html#logging"> man page</a>.
+       <p>
+
+  <dt> <b>Bug Fixes of Interest</b>
+  <dd> A number of bugs have been addressed in this release of Norm.
+       What follows is a description of those bugs that might be of
+       interest:
+  <p>
+
+  <dt><b>4965775: Norm threads should guard against lost interrupts</b><dt>
+
+  <dd> Thread subclasses in Norm that use logging and do not override the
+       <code>Thread.interrupt</code> method to set an "interrupted" field are
+       susceptable to lost interrupts.  This problem can occur because
+       <code>java.util.logging</code> swallows internal
+       <code>InterruptedIOExceptions</code> without setting the receiving
+       thread's interrupted status, effectively forgetting the interrupt.  The
+       end result is that some of Norm's threads could loop endlessly instead of       terminating, causing Norm shutdowns to hang.
+       <p>
+       This bug has been fixed.
+  </dd>
+</dl>
 
 <!-- No issues for now
 



Mime
View raw message