You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by pe...@apache.org on 2012/01/21 08:28:36 UTC

svn commit: r1234278 [9/29] - in /river/tck: ./ configs/ doc/ doc/api/ doc/api/com/ doc/api/com/sun/ doc/api/com/sun/jini/ doc/api/com/sun/jini/compat/ doc/api/com/sun/jini/compat/admin1/ doc/api/com/sun/jini/compat/admin2/ doc/api/com/sun/jini/compat/...

Added: river/tck/doc/api/overview-summary.html
URL: http://svn.apache.org/viewvc/river/tck/doc/api/overview-summary.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/api/overview-summary.html (added)
+++ river/tck/doc/api/overview-summary.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,157 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--NewPage-->
+<HTML>
+<HEAD>
+<!-- Generated by javadoc (build 1.4.2) on Wed Sep 14 16:06:45 EDT 2005 -->
+<TITLE>
+Overview (Jini(TM) Technology LDJ Kit 1.0 API Documentation)
+</TITLE>
+
+<META NAME="keywords" CONTENT="Overview, Jini<sup><font size=-2>TM</font></sup> Technology LDJ Kit 1.0 API Documentation">
+
+<LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style">
+
+<SCRIPT type="text/javascript">
+function windowTitle()
+{
+    parent.document.title="Overview (Jini(TM) Technology LDJ Kit 1.0 API Documentation)";
+}
+</SCRIPT>
+
+</HEAD>
+
+<BODY BGCOLOR="white" onload="windowTitle();">
+
+
+<!-- ========= START OF TOP NAVBAR ======= -->
+<A NAME="navbar_top"><!-- --></A>
+<A HREF="#skip-navbar_top" title="Skip navigation links"></A>
+<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
+<TR>
+<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
+<A NAME="navbar_top_firstrow"><!-- --></A>
+<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
+  <TR ALIGN="center" VALIGN="top">
+  <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> &nbsp;<FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
+  </TR>
+</TABLE>
+</TD>
+<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
+</EM>
+</TD>
+</TR>
+
+<TR>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+&nbsp;PREV&nbsp;
+&nbsp;NEXT</FONT></TD>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+  <A HREF="index.html" target="_top"><B>FRAMES</B></A>  &nbsp;
+&nbsp;<A HREF="overview-summary.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
+&nbsp;<SCRIPT type="text/javascript">
+  <!--
+  if(window==top) {
+    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
+  }
+  //-->
+</SCRIPT>
+<NOSCRIPT>
+  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
+</NOSCRIPT>
+
+</FONT></TD>
+</TR>
+</TABLE>
+<A NAME="skip-navbar_top"></A>
+<!-- ========= END OF TOP NAVBAR ========= -->
+
+<HR>
+<CENTER>
+<H1>
+Jini<sup><font size=-2>TM</font></sup> Technology LDJ Kit 1.0 API Documentation
+</H1>
+</CENTER>
+
+<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
+<TR BGCOLOR="#CCCCFF" CLASS="TableHeadingColor">
+<TD COLSPAN=2><FONT SIZE="+2">
+<B>Packages</B></FONT></TD>
+</TR>
+<TR BGCOLOR="white" CLASS="TableRowColor">
+<TD WIDTH="20%"><B><A HREF="com/sun/jini/compat/admin1/package-summary.html">com.sun.jini.compat.admin1</A></B></TD>
+<TD>This package contains admin implementations for the services that ship
+with the Jini(TM) Technology Starter Kit, v1.2.1.</TD>
+</TR>
+<TR BGCOLOR="white" CLASS="TableRowColor">
+<TD WIDTH="20%"><B><A HREF="com/sun/jini/compat/admin2/package-summary.html">com.sun.jini.compat.admin2</A></B></TD>
+<TD>This package contains admin implementations for the services that ship
+with the Jini(TM) Technology Starter Kit, v2.0 and later.</TD>
+</TR>
+<TR BGCOLOR="white" CLASS="TableRowColor">
+<TD WIDTH="20%"><B><A HREF="com/sun/jini/compat/harness/package-summary.html">com.sun.jini.compat.harness</A></B></TD>
+<TD>This package contains the test harness component of the Jini(TM) Technology Lookup, Discovery, and Join Compatibility Kit.</TD>
+</TR>
+</TABLE>
+
+<P>
+&nbsp;<HR>
+
+
+<!-- ======= START OF BOTTOM NAVBAR ====== -->
+<A NAME="navbar_bottom"><!-- --></A>
+<A HREF="#skip-navbar_bottom" title="Skip navigation links"></A>
+<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
+<TR>
+<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
+<A NAME="navbar_bottom_firstrow"><!-- --></A>
+<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
+  <TR ALIGN="center" VALIGN="top">
+  <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> &nbsp;<FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
+  </TR>
+</TABLE>
+</TD>
+<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
+</EM>
+</TD>
+</TR>
+
+<TR>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+&nbsp;PREV&nbsp;
+&nbsp;NEXT</FONT></TD>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+  <A HREF="index.html" target="_top"><B>FRAMES</B></A>  &nbsp;
+&nbsp;<A HREF="overview-summary.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
+&nbsp;<SCRIPT type="text/javascript">
+  <!--
+  if(window==top) {
+    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
+  }
+  //-->
+</SCRIPT>
+<NOSCRIPT>
+  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
+</NOSCRIPT>
+
+</FONT></TD>
+</TR>
+</TABLE>
+<A NAME="skip-navbar_bottom"></A>
+<!-- ======== END OF BOTTOM NAVBAR ======= -->
+
+<HR>
+Copyright 2005, Sun Microsystems, Inc.<br> Licensed under the <a href=http://www.apache.org/licenses/LICENSE-2.0>Apache License, Version 2.0</a>.
+</BODY>
+</HTML>

Propchange: river/tck/doc/api/overview-summary.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/api/overview-tree.html
URL: http://svn.apache.org/viewvc/river/tck/doc/api/overview-tree.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/api/overview-tree.html (added)
+++ river/tck/doc/api/overview-tree.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,165 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--NewPage-->
+<HTML>
+<HEAD>
+<!-- Generated by javadoc (build 1.4.2) on Wed Sep 14 16:06:44 EDT 2005 -->
+<TITLE>
+Class Hierarchy (Jini(TM) Technology LDJ Kit 1.0 API Documentation)
+</TITLE>
+
+
+<LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style">
+
+<SCRIPT type="text/javascript">
+function windowTitle()
+{
+    parent.document.title="Class Hierarchy (Jini(TM) Technology LDJ Kit 1.0 API Documentation)";
+}
+</SCRIPT>
+
+</HEAD>
+
+<BODY BGCOLOR="white" onload="windowTitle();">
+
+
+<!-- ========= START OF TOP NAVBAR ======= -->
+<A NAME="navbar_top"><!-- --></A>
+<A HREF="#skip-navbar_top" title="Skip navigation links"></A>
+<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
+<TR>
+<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
+<A NAME="navbar_top_firstrow"><!-- --></A>
+<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
+  <TR ALIGN="center" VALIGN="top">
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> &nbsp;<FONT CLASS="NavBarFont1Rev"><B>Tree</B></FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
+  </TR>
+</TABLE>
+</TD>
+<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
+</EM>
+</TD>
+</TR>
+
+<TR>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+&nbsp;PREV&nbsp;
+&nbsp;NEXT</FONT></TD>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+  <A HREF="index.html" target="_top"><B>FRAMES</B></A>  &nbsp;
+&nbsp;<A HREF="overview-tree.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
+&nbsp;<SCRIPT type="text/javascript">
+  <!--
+  if(window==top) {
+    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
+  }
+  //-->
+</SCRIPT>
+<NOSCRIPT>
+  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
+</NOSCRIPT>
+
+</FONT></TD>
+</TR>
+</TABLE>
+<A NAME="skip-navbar_top"></A>
+<!-- ========= END OF TOP NAVBAR ========= -->
+
+<HR>
+<CENTER>
+<H2>
+Hierarchy For All Packages</H2>
+</CENTER>
+<DL>
+<DT><B>Package Hierarchies:</B><DD><A HREF="com/sun/jini/compat/admin1/package-tree.html">com.sun.jini.compat.admin1</A>, <A HREF="com/sun/jini/compat/admin2/package-tree.html">com.sun.jini.compat.admin2</A>, <A HREF="com/sun/jini/compat/harness/package-tree.html">com.sun.jini.compat.harness</A></DL>
+<HR>
+<H2>
+Class Hierarchy
+</H2>
+<UL>
+<LI TYPE="circle">class java.lang.Object<UL>
+<LI TYPE="circle">class com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/Config.html" title="class in com.sun.jini.compat.harness"><B>Config</B></A><LI TYPE="circle">class com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/DefaultAdmin.html" title="class in com.sun.jini.compat.harness"><B>DefaultAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicAdmin.html" title="interface in com.sun.jini.compat.harness">BasicAdmin</A>)
+<UL>
+<LI TYPE="circle">class com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/DefaultClientAdmin.html" title="class in com.sun.jini.compat.harness"><B>DefaultClientAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicClientAdmin.html" title="interface in com.sun.jini.compat.harness">BasicClientAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/DefaultLookupAdmin.html" title="class in com.sun.jini.compat.harness"><B>DefaultLookupAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicLookupAdmin.html" title="interface in com.sun.jini.compat.harness">BasicLookupAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/DefaultServiceAdmin.html" title="class in com.sun.jini.compat.harness"><B>DefaultServiceAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+</UL>
+<LI TYPE="circle">class com.sun.jini.compat.admin2.<A HREF="com/sun/jini/compat/admin2/ExecServiceAdmin.html" title="class in com.sun.jini.compat.admin2"><B>ExecServiceAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicLookupAdmin.html" title="interface in com.sun.jini.compat.harness">BasicLookupAdmin</A>, com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/FiddlerAdmin.html" title="class in com.sun.jini.compat.admin1"><B>FiddlerAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/MahaloAdmin.html" title="class in com.sun.jini.compat.admin1"><B>MahaloAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/MercuryAdmin.html" title="class in com.sun.jini.compat.admin1"><B>MercuryAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/NormAdmin.html" title="class in com.sun.jini.compat.admin1"><B>NormAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/OutriggerAdmin.html" title="class in com.sun.jini.compat.admin1"><B>OutriggerAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/ReggieAdmin.html" title="class in com.sun.jini.compat.admin1"><B>ReggieAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicLookupAdmin.html" title="interface in com.sun.jini.compat.harness">BasicLookupAdmin</A>, com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/ReggieServiceAdmin.html" title="class in com.sun.jini.compat.admin1"><B>ReggieServiceAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.admin2.<A HREF="com/sun/jini/compat/admin2/ServiceDestroyer.html" title="class in com.sun.jini.compat.admin2"><B>ServiceDestroyer</B></A><LI TYPE="circle">class com.sun.jini.compat.admin2.<A HREF="com/sun/jini/compat/admin2/ServiceStarterAdmin.html" title="class in com.sun.jini.compat.admin2"><B>ServiceStarterAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicLookupAdmin.html" title="interface in com.sun.jini.compat.harness">BasicLookupAdmin</A>, com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+<LI TYPE="circle">class com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/SysConfig.html" title="class in com.sun.jini.compat.harness"><B>SysConfig</B></A><LI TYPE="circle">class com.sun.jini.compat.admin1.<A HREF="com/sun/jini/compat/admin1/TransientServiceAdmin.html" title="class in com.sun.jini.compat.admin1"><B>TransientServiceAdmin</B></A> (implements com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness">BasicServiceAdmin</A>)
+</UL>
+</UL>
+<H2>
+Interface Hierarchy
+</H2>
+<UL>
+<LI TYPE="circle">interface com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicAdmin.html" title="interface in com.sun.jini.compat.harness"><B>BasicAdmin</B></A><UL>
+<LI TYPE="circle">interface com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicClientAdmin.html" title="interface in com.sun.jini.compat.harness"><B>BasicClientAdmin</B></A><LI TYPE="circle">interface com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicLookupAdmin.html" title="interface in com.sun.jini.compat.harness"><B>BasicLookupAdmin</B></A><LI TYPE="circle">interface com.sun.jini.compat.harness.<A HREF="com/sun/jini/compat/harness/BasicServiceAdmin.html" title="interface in com.sun.jini.compat.harness"><B>BasicServiceAdmin</B></A></UL>
+</UL>
+<HR>
+
+
+<!-- ======= START OF BOTTOM NAVBAR ====== -->
+<A NAME="navbar_bottom"><!-- --></A>
+<A HREF="#skip-navbar_bottom" title="Skip navigation links"></A>
+<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
+<TR>
+<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
+<A NAME="navbar_bottom_firstrow"><!-- --></A>
+<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
+  <TR ALIGN="center" VALIGN="top">
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> &nbsp;<FONT CLASS="NavBarFont1Rev"><B>Tree</B></FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
+  </TR>
+</TABLE>
+</TD>
+<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
+</EM>
+</TD>
+</TR>
+
+<TR>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+&nbsp;PREV&nbsp;
+&nbsp;NEXT</FONT></TD>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+  <A HREF="index.html" target="_top"><B>FRAMES</B></A>  &nbsp;
+&nbsp;<A HREF="overview-tree.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
+&nbsp;<SCRIPT type="text/javascript">
+  <!--
+  if(window==top) {
+    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
+  }
+  //-->
+</SCRIPT>
+<NOSCRIPT>
+  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
+</NOSCRIPT>
+
+</FONT></TD>
+</TR>
+</TABLE>
+<A NAME="skip-navbar_bottom"></A>
+<!-- ======== END OF BOTTOM NAVBAR ======= -->
+
+<HR>
+Copyright 2005, Sun Microsystems, Inc.<br> Licensed under the <a href=http://www.apache.org/licenses/LICENSE-2.0>Apache License, Version 2.0</a>.
+</BODY>
+</HTML>

Propchange: river/tck/doc/api/overview-tree.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/api/package-list
URL: http://svn.apache.org/viewvc/river/tck/doc/api/package-list?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/api/package-list (added)
+++ river/tck/doc/api/package-list Sat Jan 21 07:28:27 2012
@@ -0,0 +1,3 @@
+com.sun.jini.compat.admin1
+com.sun.jini.compat.admin2
+com.sun.jini.compat.harness

Added: river/tck/doc/api/packages.html
URL: http://svn.apache.org/viewvc/river/tck/doc/api/packages.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/api/packages.html (added)
+++ river/tck/doc/api/packages.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,37 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--NewPage-->
+<HTML>
+<HEAD>
+<!-- Generated by javadoc (build 1.4.2) on Wed Sep 14 16:06:45 EDT 2005 -->
+<TITLE>
+ (Jini(TM) Technology LDJ Kit 1.0 API Documentation)
+</TITLE>
+
+
+<LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style">
+
+<SCRIPT type="text/javascript">
+function windowTitle()
+{
+    parent.document.title=" (Jini(TM) Technology LDJ Kit 1.0 API Documentation)";
+}
+</SCRIPT>
+
+</HEAD>
+
+<BODY BGCOLOR="white" onload="windowTitle();">
+
+<BR>
+
+<BR>
+
+<BR>
+<CENTER>
+The front page has been relocated.Please see:
+<BR>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Frame version</A>
+<BR>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="overview-summary.html">Non-frame version.</A></CENTER>
+
+</BODY>
+</HTML>

Propchange: river/tck/doc/api/packages.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/api/resources/inherit.gif
URL: http://svn.apache.org/viewvc/river/tck/doc/api/resources/inherit.gif?rev=1234278&view=auto
==============================================================================
Binary file - no diff available.

Propchange: river/tck/doc/api/resources/inherit.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: river/tck/doc/api/serialized-form.html
URL: http://svn.apache.org/viewvc/river/tck/doc/api/serialized-form.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/api/serialized-form.html (added)
+++ river/tck/doc/api/serialized-form.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,132 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--NewPage-->
+<HTML>
+<HEAD>
+<!-- Generated by javadoc (build 1.4.2) on Wed Sep 14 16:06:47 EDT 2005 -->
+<TITLE>
+Serialized Form (Jini(TM) Technology LDJ Kit 1.0 API Documentation)
+</TITLE>
+
+
+<LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style">
+
+<SCRIPT type="text/javascript">
+function windowTitle()
+{
+    parent.document.title="Serialized Form (Jini(TM) Technology LDJ Kit 1.0 API Documentation)";
+}
+</SCRIPT>
+
+</HEAD>
+
+<BODY BGCOLOR="white" onload="windowTitle();">
+
+
+<!-- ========= START OF TOP NAVBAR ======= -->
+<A NAME="navbar_top"><!-- --></A>
+<A HREF="#skip-navbar_top" title="Skip navigation links"></A>
+<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
+<TR>
+<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
+<A NAME="navbar_top_firstrow"><!-- --></A>
+<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
+  <TR ALIGN="center" VALIGN="top">
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
+  </TR>
+</TABLE>
+</TD>
+<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
+</EM>
+</TD>
+</TR>
+
+<TR>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+&nbsp;PREV&nbsp;
+&nbsp;NEXT</FONT></TD>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+  <A HREF="index.html" target="_top"><B>FRAMES</B></A>  &nbsp;
+&nbsp;<A HREF="serialized-form.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
+&nbsp;<SCRIPT type="text/javascript">
+  <!--
+  if(window==top) {
+    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
+  }
+  //-->
+</SCRIPT>
+<NOSCRIPT>
+  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
+</NOSCRIPT>
+
+</FONT></TD>
+</TR>
+</TABLE>
+<A NAME="skip-navbar_top"></A>
+<!-- ========= END OF TOP NAVBAR ========= -->
+
+<HR>
+<CENTER>
+<H1>
+Serialized Form</H1>
+</CENTER>
+<HR>
+
+
+<!-- ======= START OF BOTTOM NAVBAR ====== -->
+<A NAME="navbar_bottom"><!-- --></A>
+<A HREF="#skip-navbar_bottom" title="Skip navigation links"></A>
+<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
+<TR>
+<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
+<A NAME="navbar_bottom_firstrow"><!-- --></A>
+<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
+  <TR ALIGN="center" VALIGN="top">
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
+  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
+  </TR>
+</TABLE>
+</TD>
+<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
+</EM>
+</TD>
+</TR>
+
+<TR>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+&nbsp;PREV&nbsp;
+&nbsp;NEXT</FONT></TD>
+<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
+  <A HREF="index.html" target="_top"><B>FRAMES</B></A>  &nbsp;
+&nbsp;<A HREF="serialized-form.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
+&nbsp;<SCRIPT type="text/javascript">
+  <!--
+  if(window==top) {
+    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
+  }
+  //-->
+</SCRIPT>
+<NOSCRIPT>
+  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
+</NOSCRIPT>
+
+</FONT></TD>
+</TR>
+</TABLE>
+<A NAME="skip-navbar_bottom"></A>
+<!-- ======== END OF BOTTOM NAVBAR ======= -->
+
+<HR>
+Copyright 2005, Sun Microsystems, Inc.<br> Licensed under the <a href=http://www.apache.org/licenses/LICENSE-2.0>Apache License, Version 2.0</a>.
+</BODY>
+</HTML>

Propchange: river/tck/doc/api/serialized-form.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/api/stylesheet.css
URL: http://svn.apache.org/viewvc/river/tck/doc/api/stylesheet.css?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/api/stylesheet.css (added)
+++ river/tck/doc/api/stylesheet.css Sat Jan 21 07:28:27 2012
@@ -0,0 +1,29 @@
+/* Javadoc style sheet */
+
+/* Define colors, fonts and other style attributes here to override the defaults */
+
+/* Page background color */
+body { background-color: #FFFFFF }
+
+/* Headings */
+h1 { font-size: 145% }
+
+/* Table colors */
+.TableHeadingColor     { background: #CCCCFF } /* Dark mauve */
+.TableSubHeadingColor  { background: #EEEEFF } /* Light mauve */
+.TableRowColor         { background: #FFFFFF } /* White */
+
+/* Font used in left-hand frame lists */
+.FrameTitleFont   { font-size: 100%; font-family: Helvetica, Arial, sans-serif }
+.FrameHeadingFont { font-size:  90%; font-family: Helvetica, Arial, sans-serif }
+.FrameItemFont    { font-size:  90%; font-family: Helvetica, Arial, sans-serif }
+
+/* Navigation bar fonts and colors */
+.NavBarCell1    { background-color:#EEEEFF;} /* Light mauve */
+.NavBarCell1Rev { background-color:#00008B;} /* Dark Blue */
+.NavBarFont1    { font-family: Arial, Helvetica, sans-serif; color:#000000;}
+.NavBarFont1Rev { font-family: Arial, Helvetica, sans-serif; color:#FFFFFF;}
+
+.NavBarCell2    { font-family: Arial, Helvetica, sans-serif; background-color:#FFFFFF;}
+.NavBarCell3    { font-family: Arial, Helvetica, sans-serif; background-color:#FFFFFF;}
+

Propchange: river/tck/doc/api/stylesheet.css
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/commandline.html
URL: http://svn.apache.org/viewvc/river/tck/doc/commandline.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/commandline.html (added)
+++ river/tck/doc/commandline.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,199 @@
+<!--
+ ! 
+ ! Copyright 2005, Sun Microsystems, Inc.
+ ! Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+ ! Apache License, Version 2.0</a>.
+ ! 
+ !-->
+<HTML>
+<HEAD>
+   <TITLE>LDJ Kit Command-line Usage</TITLE>
+</HEAD>
+<BODY BGCOLOR="#FFFFFF">
+<center>
+<H1>Command-line Usage for the Jini(TM)
+Technology Lookup, Discovery, and Join Compatibility Kit<br>
+v1.0</H1>
+</center>
+<H2>
+SYNOPSIS</H2>
+
+<blockquote><code>java</code> 
+      <code>-Djava.security.policy=</code><i>&lt;security-policy-property&gt;</i>
+      <code>-cp</code> <i>&lt;classpath&gt;&nbsp;</i>
+      <code>com.sun.jini.compat.harness.Runner </code>
+      <i>&lt;full-path-to-config-file-name&gt;&nbsp;</i>
+      <code>[-categories </code><i>c1</i><code>,...] 
+            [-tests </code><i>t1</i><code>,...]
+            [-xcategories </code><i>c1</i><code>,...]
+            [-xtests </code><i>t1</i><code>,...]
+            [-noduplicates]</code>
+</blockquote>
+
+<H2>
+DESCRIPTION</H2>
+
+The harness found in the Jini(TM) Technology Lookup, Discovery, and 
+Join Compatibility Kit (LDJ Kit) is used to test 
+clients, services, and lookup services for conformance to the 
+Jini technology specifications. 
+
+<H2>
+OPTIONS AND ARGUMENTS</H2>
+
+<blockquote>
+<dl>
+
+   <dt><b><i><code>security-policy-property</code></i></dt></b>
+   <dd>The security policy file that
+   is specified for the <code>Runner</code> program must be the
+   <code>policy.all</code> found in the <code>policy</code> subdirectory
+   of the LDJ Kit installation directory.</dd><p>
+
+   <dt><b><i><code>classpath</code></i></dt></b>
+   <dd>The classpath will need to include the
+   <code>compat.jar</code> file, located in the <code>lib</code>
+   subdirectory of the LDJ Kit installation directory, as well as any
+   implementation(s) of Admin components that you've written.</dd><p>
+
+   <dt><b><i><code>full-path-to-config-file-name</code></i></dt></b>
+   <dd>Specifies the absolute path of the LDJ Kit configuration file.
+       A sample configuration file (<code>ldj.prop</code>) is in
+       the LDJ Kit installation directory.</dd><p>
+
+   <dt><b><code>categories</code></b> 
+       <dd>Specifies a comma-separated list of test categories. When the 
+           test list is generated, only tests for the given 
+           categories will be included. This argument is optional, but 
+           if it is not provided, then the property 
+           <code>com.sun.jini.compat.categories</code> must exist in the
+           config file and must specify a comma-separated list of test 
+           categories. Valid values for this property are <code>client</code>,
+           <code>service</code>, and <code>lookup</code>.<p>
+
+   <dt><b><code>tests</code></b>
+       <dd>Specifies a comma-separated list of tests or test sets to run.  
+           If <code>tests</code> is not specified, all LDJ Kit tests which
+           support the specified <code>categories</code> are included.
+           The tests in each category are:
+<P>
+<B>client</B><BR>
+<CODE>
+com.sun.jini.compat.test.RequestPacketTest<BR>
+com.sun.jini.compat.test.UnicastRequestTest<BR>
+com.sun.jini.compat.test.CodeDownloadTest<BR>
+</CODE>
+<P>
+<B>service</B><BR>
+<CODE>
+com.sun.jini.compat.test.RequestPacketTest<BR>
+com.sun.jini.compat.test.UnicastRequestTest<BR>
+com.sun.jini.compat.test.CodeDownloadTest<BR>
+com.sun.jini.compat.test.AnnouncementResponseTest<BR>
+com.sun.jini.compat.test.RegistrationTest<BR>
+com.sun.jini.compat.test.MultiRegistrationTest<BR>
+com.sun.jini.compat.test.PublicGroupTest<BR>
+com.sun.jini.compat.test.NonPublicGroupTest<BR>
+com.sun.jini.compat.test.MultiGroupTest<BR>
+com.sun.jini.compat.test.LeaseTest<BR>
+</CODE>
+<P>
+<B>lookup</B><BR>
+<CODE>
+com.sun.jini.compat.test.LookupByServiceIDTest<BR>
+com.sun.jini.compat.test.LookupByClassTest<BR>
+com.sun.jini.compat.test.LookupBySuperClassTest<BR>
+com.sun.jini.compat.test.LookupByInterfaceTest<BR>
+com.sun.jini.compat.test.MultipleServiceLeaseRenewalTest<BR>
+com.sun.jini.compat.test.ServiceIDTest<BR>
+com.sun.jini.compat.test.ServiceLeaseExpirationTest<BR>
+com.sun.jini.compat.test.MultipleEventLeaseRenewalTest<BR>
+com.sun.jini.compat.test.EventLeaseExpirationTest<BR>
+</CODE>
+
+<p>
+
+   <dt><b><code>xtests</code></b>
+       <dd>Specifies a comma-separated list of tests to exclude from the 
+           test list.<p>
+
+   <dt><b><code>xcategories</code></b> 
+       <dd>Specifies a comma-separated list of categories to exclude from 
+           the test list.<p>
+
+   <dt><b><code>noduplicates</code></b> 
+       <dd>Specifies that duplicate test entries are to be removed from 
+           the test list. By default, duplicates are retained.<p>
+</dl>
+</blockquote>
+
+<H3>
+RELATED SYSTEM PROPERTIES</H3>
+<blockquote>
+
+<dl>
+
+<dt><b><code>com.sun.jini.compat.reggie.proxy.debug</code></b>
+<dd>If set to any value, this property indicates that debugging
+information related to the execution of the LDJ Kit's lookup service proxy should be
+printed to <code>System.err</code>. Set this property on <i>the LDJ Kit</i> command line, if
+calls to the lookup service are unexpectedly returning
+<code>null</code> values for service objects, service types, attribute
+set classes, attribute sets, or attribute values.
+</dl></blockquote>
+
+<H2>
+EXAMPLES</H2>
+<ul>
+<li>  To run each of the tests that a service must pass (where &lt;install dir&gt; is the installation directory of the LDJ Kit)
+<p>  On UNIX platforms:
+<pre>
+	java -Djava.security.policy=&lt;install dir&gt;/policy/policy.all 
+	     -cp &lt;install dir&gt;/lib/compat.jar
+	     com.sun.jini.compat.harness.Runner 
+             &lt;install dir&gt;/ldj.prop
+             -categories service    
+</pre>
+    On Microsoft Windows platforms:
+<pre>
+	java -Djava.security.policy=&lt;install dir&gt;\policy\policy.all
+	     -cp &lt;install dir&gt;\lib\compat.jar
+	     com.sun.jini.compat.harness.Runner
+	     &lt;install dir&gt;\ldj.prop
+             -categories service
+</pre>
+
+<li> To run only the service test, <code>RegistrationTest</code> (where &lt;install dir&gt; is the installation directory of the LDJ Kit)
+<p>  On UNIX platforms:
+<pre>
+	java -Djava.security.policy=&lt;install dir&gt;/policy/policy.all 
+	     -cp &lt;install dir&gt;/lib/compat.jar
+	     com.sun.jini.compat.harness.Runner 
+             &lt;install dir&gt;/ldj.prop
+             -tests com.sun.jini.compat.test.RegistrationTest   
+</pre>
+    On Microsoft Windows platform:
+<pre>
+	java -Djava.security.policy=&lt;install dir&gt;\policy\policy.all
+	     -cp &lt;install dir&gt;\lib\compat.jar
+	     com.sun.jini.compat.harness.Runner
+	     &lt;install dir&gt;\ldj.prop
+             -tests com.sun.jini.compat.test.RegistrationTest
+</pre>
+
+where <code>com.sun.jini.compat.test.RegistrationTest</code>
+could be replaced with any of the individual LDJ Kit tests listed in the
+<A HREF="test-spec.html"><i>Jini(TM)
+Technology Lookup, Discovery, and Join Compatibility Kit Test Descriptions</A></i>.
+</blockquote>
+</ul>
+
+
+<hr>
+
+Copyright 2005, Sun Microsystems, Inc.<br>
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+Apache License, Version 2.0</a>.
+
+</body>
+</html>

Propchange: river/tck/doc/commandline.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/faq.html
URL: http://svn.apache.org/viewvc/river/tck/doc/faq.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/faq.html (added)
+++ river/tck/doc/faq.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,366 @@
+<!--
+ ! 
+ ! Copyright 2005, Sun Microsystems, Inc.
+ ! Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+ ! Apache License, Version 2.0</a>.
+ ! 
+ !-->
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML>
+<HEAD>
+<TITLE>
+Jini LDJ Kit FAQ
+</TITLE>
+</HEAD>
+<BODY bgcolor="#FFFFFF">
+<TR>
+  <TD><!-- INSERT SUB-NAV INFO -->
+  </TD>
+</TR>
+<!-- END SUB-NAV -->
+</TABLE>
+<!-- Template Version 2.0 -->
+<!-- ================== -->
+<!-- Start Main Content -->
+<!-- ================== -->
+
+<H1><CENTER>Jini(TM) Technology Lookup, Discovery, and Join Compatibility Kit<BR> 
+Frequently Asked Questions<BR>
+v1.0</CENTER></H1>
+
+<P><a href="#overview">OVERVIEW</a>
+<UL>
+<LI><a href="#what">What is the Jini(TM) Technology Lookup, Discovery, and Join Compatibility Kit?</a>
+<LI><a href="#why">Why should I use the LDJ Kit to test my program?</a>
+<LI><a href="#where">How can I get the LDJ Kit?</a>
+</UL>
+<P><a href="#running">RUNNING THE LDJ KIT</a>
+<UL>
+<LI><a href="#version">Which version of the LDJ Kit should I use?</a>
+<LI><a href="#SDK">Which SDK and operating system should I use to test my program?</a>
+<LI><a href="#category">Which LDJ Kit tests (or test categories) must I pass?</a>
+<LI><a href="#platforms">On which platforms do I have to pass the LDJ Kit?</a>
+<LI><a href="#allpass">Does every possible configuration of my service need to pass the LDJ Kit?</a>
+<LI><a href="#official">What is an "official run" of the LDJ Kit?</a>
+<LI><a href="#time">How long does it take to run the LDJ Kit?</a>
+<LI><a href="#shorten">How can I shorten these test times for experimental and debugging purposes?</a>
+<LI><a href="#automate">How can I automate LDJ Kit testing for my program?</a>
+</UL>
+<P><a href="#compatadmins">LDJ KIT ADMINS</a>
+<UL>
+<LI><a href="#admin">What is an "Admin"?</a>
+<LI><a href="#implement">Can I implement my own Admin object?</a>
+<LI><a href="#myimpl">How do I implement my own Admin object?</a>
+</UL>
+<P><a href="#common">COMMON PROBLEMS</a>
+<UL>
+<LI><a href="#watchout">What are some things to watch out for when running the LDJ Kit?</a>
+</UL>
+<P><a href="#troubleshooting">TROUBLESHOOTING</a>
+<UL>
+<LI><a href="#NPE">Why do I fail (or get a <CODE>NullPointerException</CODE>) when I run the <CODE>RegistrationTest</CODE> or the <CODE>MultipleRegistrationTest</CODE>?</a>
+<LI><a href="#pick">My service doesn't appear to register with the LDJ Kit lookup (or when I use the <CODE>DefaultServiceAdmin</CODE>, my service is not in the list displayed by the LDJ Kit)</a>
+<LI><a href="#failing">Why am I failing a LDJ Kit test with "java.io.IOException: The system cannot find the path specified" or "java.io.IOException: The filename, directory name, or volume label syntax is incorrect"?</a>
+  
+<LI><a href="#PGT">Why am I failing the <tt>PublicGroupTest</tt>?</a>
+
+<LI><a href="#NPGT">Why am I failing the <tt>NonPublicGroupTest</tt>?</a>
+<LI><a href="#dynamic">My service uses a dynamic proxy and I'm using the LDJ Kit's <CODE>DefaultServiceAdmin</CODE>.  
+When I'm presented with the list of services, how do I know which one is mine?</a>
+<LI><a href="#CodeDownloadTest">Why is my service failing the <CODE>com.sun.jini.compat.test.CodeDownloadTest</CODE>?</a>
+</UL>
+
+
+<HR>
+<H2><a NAME="overview"></a>OVERVIEW</H2>
+
+<H3><a NAME="what"></a>What is the Jini(TM) Technology Lookup, Discovery, and Join Compatibility Kit?</H3>
+<P>
+The Jini(TM) Technology Lookup, Discovery, and Join Compatibility 
+Kit (LDJ Kit) is a set of free conformance tests, a test harness, 
+and associated documentation, produced by Sun Microsystems, Inc.
+<p>
+The purpose of compatibility testing is to ensure that programs 
+are good citizens in the environment of Jini
+technology-enabled services and/or devices (good lookup citizens). To
+be a good lookup citizen, a program must interoperate with other good
+lookup citizens and behave in a way that doesn't cause trouble for the
+rest of the networks, such as swamping a network with too much traffic.
+The rules of good citizenship are detailed in the Jini technology
+specifications and are, to a lesser extent, codified in the LDJ Kit.
+<p>
+This kit may <b>not</b> be used to fulfill
+any compliance requirements for code licensed under the
+Sun Community Source License v3.0/Jini Technology Specific 
+Attachment v1.0 (SCSL3/Jini TSA 1.0).
+<P>
+<H3><a NAME="why"></a>Why should I use the LDJ Kit to test my program?</H3>
+<P>
+The LDJ Kit is a free test suite that helps to ensure that your Jini technology-enabled client, service, or lookup service (hereafter referred to as "program") conforms with some very basic, but critical, Jini specification 
+requirements.  For more information on specifications covered by individual tests, see the
+<I>Jini Technology Lookup, Discovery, and Join 
+Compatibility Kit Test Descriptions</I> document found in the LDJ Kit download.
+<p>
+This kit may <b>not</b> be used to fulfill
+any compliance requirements for code licensed under the
+Sun Community Source License v3.0/Jini Technology Specific 
+Attachment v1.0 (SCSL3/Jini TSA 1.0).
+<P>
+<H3><a NAME="where"></a>How can I get the LDJ Kit?</H3>
+<P>
+The LDJ Kit is freely available from <CODE><a href="http://starterkit.jini.org">
+http://starterkit.jini.org</a></CODE>.
+
+<HR>
+<H2><a NAME="running"></a>RUNNING THE LDJ KIT</H2>
+
+<H3><a NAME="version"></a>Which version of the LDJ Kit should I use?</H3>
+<P>
+You should use the latest LDJ Kit available at the download site listed above.
+<P>
+<H3><a NAME="SDK"></a>Which JDK and operating system should I use to test my program?</H3>
+<P>
+While you may use Java(TM) 2 SDK, v1.2.2 or later on any operating system configuration, we recommend that you use a platform on which the LDJ Kit has been tested if you encounter problems. These tested platforms are listed at
+<a href="http://java.sun.com/developer/products/jini/tested.html">
+http://java.sun.com/developer/products/jini/tested.html</a>.
+<P>
+<H3><a NAME="category"></a>Which LDJ Kit tests (or test categories) should I run?</H3>
+<P>
+You should run all the tests in all the categories that apply to your program.  For example, if your program is a Jini technology-enabled service <i>(Jini service)</i> that also acts as a Jini technology-enabled client <i>(Jini client)</i>, then you should run both the client and service tests against your program.  If your program is a Jini lookup
+service that also acts as a Jini service (registers in other lookups), then you should run both the service and lookup tests against your program. The tests contained in each category are:
+<table BORDER=0 CELLSPACING=10 WIDTH="100%" NOSAVE >
+<tr NOSAVE>
+<td NOSAVE><B><nobr>service</nobr></B><pre>
+com.sun.jini.compat.test.RequestPacketTest
+com.sun.jini.compat.test.UnicastRequestTest
+com.sun.jini.compat.test.CodeDownloadTest
+com.sun.jini.compat.test.AnnouncementResponseTest
+com.sun.jini.compat.test.RegistrationTest
+com.sun.jini.compat.test.MultipleRegistrationTest
+com.sun.jini.compat.test.PublicGroupTest
+com.sun.jini.compat.test.NonPublicGroupTest
+com.sun.jini.compat.test.MultipleGroupTest
+com.sun.jini.compat.test.LeaseTest
+</pre>
+</tr> 
+<tr NOSAVE>
+<td NOSAVE><B><nobr>client</nobr></B><pre>
+com.sun.jini.compat.test.RequestPacketTest
+com.sun.jini.compat.test.UnicastRequestTest
+com.sun.jini.compat.test.CodeDownloadTest
+</pre>
+</tr> 
+<tr NOSAVE>
+<td NOSAVE><B><nobr>lookup</nobr></B><pre>
+com.sun.jini.compat.test.LookupByServiceIDTest
+com.sun.jini.compat.test.LookupByClassTest
+com.sun.jini.compat.test.LookupBySuperClassTest
+com.sun.jini.compat.test.LookupByInterfaceTest
+com.sun.jini.compat.test.MultipleServiceLeaseRenewalTest
+com.sun.jini.compat.test.ServiceLeaseExpirationTest
+com.sun.jini.compat.test.ServiceIDTest
+com.sun.jini.compat.test.MultipleEventLeaseRenewalTest
+com.sun.jini.compat.test.EventLeaseExpirationTest
+</pre>
+</tr> 
+</table>
+
+<P>
+<H3><a NAME="platforms"></a>On which platforms should I run the LDJ Kit?</H3>
+<P>
+You should run the LDJ Kit on at least one platform that supports Java 2 SDK, v1.2.2 or later. Which platform you use is entirely your choice.
+<P>
+<H3><a NAME="allpass"></a>Under which configurations should I start my program when running the LDJ Kit tests?</H3>
+<P>
+To pass the LDJ Kit tests, Jini clients, services, and lookup services must be able to abide by the LDJ Kit good citizenship requirements, such as discovering and joining only lookup services in the "public" group. It is not required that every possible configuration be capable of passing the LDJ Kit, nor is it required that your program's default configuration be capable of passing; it is simply required that at least one configuration be capable of passing.  If your service implementation uses the <code>net.jini.lookup.JoinManager</code> to handle Jini discovery and join functions, this requirement of the LDJ Kit should be easily met.
+
+
+<P>
+<H3><a NAME="official"></a>What is an "official run" of the LDJ Kit?</H3>
+<P>An official run of the LDJ Kit is a single execution of the LDJ Kit test suite that meets certain requirements.  These requirements are described in 
+<i>Passing the Jini Technology Lookup, Discovery, and Join 
+Compatibility Kit</i>, Section 2.1, found in the LDJ Kit download.
+<P>
+<H3><a NAME="time"></a>How long does it take to run the LDJ Kit?</H3>
+<P>A successful official run of the three LDJ Kit client tests should take approximately five minutes. A successful official run of the ten LDJ Kit service tests should take approximately one hour. A successful official run of the nine LDJ Kit lookup tests should take approximately 30 minutes.
+<P>
+<H3><a NAME="shorten"></a>How can I shorten these test times for experimental and debugging purposes?</H3>
+<P>The LDJ Kit configuration file contains a commented-out property,
+<CODE>com.sun.jini.compat.unofficialQuietTime</CODE>, that can be used to reduce the wait time used by most tests. For an official run, the default value of 600000 milliseconds (10 minutes) or greater must be used for this property. However, for purposes of experimentation and debugging, you can reduce this to something smaller, such as 60000 milliseconds (one minute). Once you have resolved any problems, you must comment out this property to perform an official LDJ Kit run. This property is further documented in the LDJ Kit test descriptions and property file.
+<P>
+<H3><a NAME="automate"></a>How can I automate LDJ Kit testing for my program?</H3>
+<P>To automate the LDJ Kit testing for your program, you must implement your own specialized Admin object.  See the next section of this FAQ for more information on how to implement your own Admin.
+
+<HR>
+<H2><a NAME="compatadmins"></a>LDJ KIT ADMINS</H2>
+
+<H3><a NAME="admin"></a>What is an "Admin"?</H3>
+<P>
+An "Admin" is an object that is responsible for starting and stopping the program you are testing. The LDJ Kit comes with three default Admins (one each for clients, services, and lookup services), which simply ask you to start and stop your program at the appropriate times determined by each test.
+<P>
+<H3><a NAME="implement"></a>Can I implement my own Admin object?</H3>
+<P>
+Yes!  In fact it may be necessary to implement your own Admin in certain circumstances where the supplied default Admins do not work for your program. In addition, if you wish to automate LDJ Kit testing of your program, you will need to implement your own, specialized Admin object to start and stop your program automatically.  To help you get started, the LDJ Kit download includes, as examples, the Admins used to automatically test the services found in the Jini(TM) Technology Starter Kit, v1.2.1_001 and v2.1.  See the API docs and source files for the <code>com.sun.jini.compat.admin1</code> and <code>com.sun.jini.compat.admin2</code> packages in the LDJ Kit download.
+<P>
+<H3><a NAME="myimpl"></a>How do I implement my own Admin object?</H3>
+<P>
+See <i>Implementing the Jini Technology Lookup, Discovery, and Join 
+Compatibility Kit, v1.0 Admin Interface</i>, found in the LDJ Kit download.
+
+<HR>
+<H2><a NAME="common"></a>COMMON PROBLEMS</H2>
+
+<H3><a NAME="watchout"></a>What are some things to watch out for when running the LDJ Kit?</H3>
+<UL>
+<LI>Make sure <CODE>rmid</CODE> is started on the machine on which you are running the LDJ Kit.
+<LI>Make sure no HTTP server is using port 8080 on the machine on which you are running the LDJ Kit (the HTTP server started by the LDJ Kit uses port 8080).
+<LI>If your program contains downloadable classes, you must run your 
+    own HTTP server to support the downloading of these classes.
+<LI>Make sure that the directory you specified in the configuration file as the value of the <CODE>com.sun.jini.compat.scratchDir</CODE> is in the correct format for the operating system on which you are testing and that you have permission to write to the specified directory.
+<LI>Make sure that the paths in the LDJ Kit configuration file use the correct file separator format (for example, two backslashes '\\' on Microsoft Windows platforms).
+<LI>If you are using the <CODE>DefaultServiceAdmin</CODE>, make sure you select the correct service from the list that is displayed  by the LDJ Kit's <CODE>DefaultServiceAdmin</CODE>.
+<LI>If you suspect you are having codebase problems, pass the property <tt>-Dcom.sun.jini.<b>compat</b>.reggie.proxy.debug=true</tt> to the LDJ Kit virtual machine (VM) (you may also find the <tt>-Dnet.jini.discovery.debug=true</tt> helpful). If codebase is the problem, you will see one or more exceptions that should help you determine the problem.
+</UL>
+<HR>
+<H2><a NAME="troubleshooting"></a>TROUBLESHOOTING</H2>
+
+<P>The following questions and answers assume that you are familiar with the LDJ Kit test designs in the <I><a href="test-spec.html">Jini Technology Lookup, Discovery, and Join Compatibility Kit Test Descriptions</a></I> document found in the LDJ Kit download.
+
+
+<H3><a NAME="NPE"></a>Why do I fail (or get a <CODE>NullPointerException</CODE>) when I run the <CODE>RegistrationTest</CODE> or the <CODE>MultipleRegistrationTest</CODE>?</H3>
+
+<dl>
+<dt><B>possible cause</B>
+<dd>Service packaging problem
+<dt>detail
+<dd>If the service being tested specifies an attribute in the entry registered with the lookup service but the service's codebase does not include the attribute class, then the LDJ Kit will fail to download the attribute class.</dd>
+<dt>solution
+<dd>In general, the service's downloadable JAR files should contain ALL classes that a client might require because the service provider has no control over the <CODE>CLASSPATH</CODE> used by the service's client (in this case the LDJ Kit).
+</dd>
+</dt>
+</dl>
+
+
+
+<h3><a NAME="pick"></a>My service doesn't appear to register with the LDJ Kit lookup (or when I use the <CODE>DefaultServiceAdmin</CODE>, my service is not in the list displayed by the LDJ Kit)</h3>
+
+<dl>
+<dt><B>possible cause</B>
+<dd>The <tt>java.rmi.server.codebase</tt> property value that you specified for your service is incorrect.</dd>
+
+<dt>detail
+<dd>The <tt>DefaultServiceAdmin</tt> of the LDJ Kit is acting like a 
+Jini client, and as such is trying to obtain the proxy for the service you are testing from the LDJ Kit lookup service. In order to do 
+so, the LDJ Kit must have access to your service's classes.</dd>
+
+<dt>solution
+<dd>To verify that this is the problem, pass the property <tt>-Dcom.sun.jini.compat.reggie.proxy.debug=true</tt> to the LDJ Kit VM (you may also find the <tt>-Dnet.jini.discovery.debug=true</tt> helpful). If the codebase is the problem, you will see one or more exceptions that should help you determine the problem.</dd>
+</dt>
+</dl>
+
+
+<h3><a NAME="failing"></a>Why am I failing a LDJ Kit test with "java.io.IOException: Could not create directory" or "java.io.IOException: The filename, directory name, or volume label syntax is incorrect"?</h3>   
+<dl>
+<dt><B>possible cause</B>
+<dd>The path you specified for the LDJ Kit property <CODE>com.sun.jini.compat.scratchDir</CODE> is the wrong format for the operating system on which you are testing or you do not have permission to write to the specified directory.</dd>
+
+<dt>solution
+<dd>Make sure that the directory you specified in the configuration file as the value of the <CODE>com.sun.jini.compat.scratchDir</CODE> is in the correct format for the operating system on which you are testing and that you have permission to write to the specified directory.</dd>
+</dt>
+</dl>
+
+
+<h3><a NAME="PGT"></a>Why am I failing the <tt>PublicGroupTest</tt>?</h3>
+<dl>
+<dt><B>possible cause</B>
+<dd>Your service is not registering with the "public" lookup service group.
+
+<dt>detail
+<dd><i>Jini(TM) Discovery & Join Specification</i>, Section DJ.1.4.1, says the service "should" default to using the "public" group. The LDJ Kit was designed to verify that Jini services act as 'good citizens', and one of our decisions about what makes up a good citizen is that the service must be capable of joining the "public" group. The <CODE>PublicGroupTest</CODE> is the test that verifies this behavior.
+
+<dt>solution
+<dd>To pass this test, you must make it possible to configure your service and clients to perform multicast discovery for at least the "public" group.
+</dd>
+</dt>
+</dl>
+
+<h3><a NAME="NPGT"></a>Why am I failing the <tt>NonPublicGroupTest</tt>?</h3>
+<dl>
+<dt><B>possible cause</B>
+<dd>Your service registers in <tt>ALL_GROUPS</tt>.</dd>
+
+<dt>detail
+<dd>The test is designed to check for this behavior because your service should NOT register in <tt>ALL_GROUPS</tt>.</dd>
+
+<dt>solution
+<dd>Modify your service to not register with <CODE>ALL_GROUPS</CODE>.</dd>
+</dt>
+<p>
+<dt><B>possible cause</B>
+<dd>An identical service that registers in <tt>ALL_GROUPS</tt> is running on the network. You selected that service from the list displayed by the LDJ Kit's <tt>DefaultServiceAdmin</tt>.</dd>
+
+<dt>detail
+<dd>The LDJ Kit lookup service will allow registrations from any service on the network that specifies the group to which the lookup service belongs. Thus, a service that registers with <tt>ALL_GROUPS</tt>
+will always register in the LDJ Kit lookup service. It could be possible that an identical service to the one you are testing is running on the network and is registering with the LDJ Kit lookup service by joining <tt>ALL_GROUPS</tt>.</dd>
+
+<dt>solution
+<dd>Be very careful to select the service that you are testing or "None of the above" from the list displayed by the LDJ Kit's <tt>DefaultServiceAdmin</tt>. The class annotation of your service's proxy is included in the list and should help you determine which service is the one you are testing. The annotation will contain the IP address or name of the machine where you started your HTTP server for your service's downloadable code.</dd>
+</dt>
+<p>
+<dt><B>possible cause</B>
+<dd>When using the LDJ Kit's <tt>DefaultServiceAdmin</tt>, you inadvertently selected a service that is not the one you are testing from the pick list instead of "None of the above."</dd>
+
+<dt>detail
+<dd>For a well-behaved
+Jini service, the service should not join the LDJ Kit lookup service started by this test. Therefore, if the service you are testing is well-behaved, it should not appear in the list displayed by the LDJ Kit's <tt>DefaultServiceAdmin</tt>. So, in this case, you should select "None of the above" from the list.</dd>
+
+<dt>solution
+<dd>If the service you are testing doesn't appear in the list, select "None of the above".</dd>
+</dt>
+<p>
+<dt><B>possible cause</B>
+<dd>Your service uses a lookup locator that discovers the lookup service on the default port on the local host.
+
+<dt>detail
+<dd>In this configuration, locator discovery will find the LDJ Kit lookup service, even though it belongs to a randomly named group.
+
+<dt>solution
+<dd>Change your service so that the use of the hardcoded lookup locator is configurable and can be turned off for LDJ Kit testing. Alternatively, run the service on a different host than you run the LDJ Kit. The LDJ Kit config file provides the <tt>com.sun.jini.compat.defaultAdmin.address</tt> property, which can be set to support this.</dd>
+</dt>
+</dl>
+
+<H3><a NAME="dynamic"></a>My service uses a dynamic proxy and I'm using the LDJ Kit's <CODE>DefaultServiceAdmin</CODE>. When I'm presented with the list of services, how do I know which one is mine?</H3>
+<P>
+The <CODE>DefaultServiceAdmin</CODE> constructs each list element using the string form of the proxy's class name and the proxy's class annotation.  The dynamic proxy's class name probably starts with <CODE>$Proxy</CODE> and careful examination of the class annotation 
+should help you determine which service is the one you are testing.
+
+<H3><a NAME="CodeDownloadTest"></a>Why is my service failing the <CODE>com.sun.jini.compat.test.CodeDownloadTest</CODE>?</H3>
+<dl>
+<dt><B>possible cause</B>
+<dd>Service started in LDJ Kit's VM
+
+<dt>detail
+<dd>The LDJ Kit starts a lookup service in another VM and downloads the lookup service proxy JAR file when it unmarshals the proxy.  If you are using a custom Admin for the service being tested and your Admin starts your service in the same VM as the LDJ Kit, then your service won't download the lookup service proxy JAR file again (since it is already cached in the VM).  Thus your service fails the test.
+
+<dt>solution
+<dd>Custom Admins must not start services in the same VM as the LDJ Kit.</dd>
+</dt>
+</dl>
+
+
+<!-- ================ -->
+<!-- End Main Content -->
+<!-- ================ -->
+
+
+</FONT>
+
+<hr>
+
+Copyright 2005, Sun Microsystems, Inc.<br>
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+Apache License, Version 2.0</a>.
+
+</BODY>
+</HTML>
+

Propchange: river/tck/doc/faq.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/installation.html
URL: http://svn.apache.org/viewvc/river/tck/doc/installation.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/installation.html (added)
+++ river/tck/doc/installation.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,103 @@
+<!--
+ ! 
+ ! Copyright 2005, Sun Microsystems, Inc.
+ ! Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+ ! Apache License, Version 2.0</a>.
+ ! 
+ !-->
+<html>
+
+<head>
+
+<title>Installation Instructions</title>
+</head>
+<body text="#000000" bgcolor="#ffffff" link="#9b37cc"
+      vlink="#cc1877" alink="#ffffff">
+      
+      
+<center><h1>Jini(TM) Technology Lookup, Discovery, and Join
+Compatibility Kit Installation Instructions<br>
+v1.0</h1></center>
+
+<p>The Jini(TM) Technology Lookup, Discovery, and Join
+Compatibility Kit (LDJ Kit) is a code and documentation bundle that can be used
+to qualify certain characteristics of hardware or software based on Jini network
+technology (Jini technology).
+<p>
+The purpose of compatibility testing is to ensure that programs are good citizens in the environment of Jini
+technology-enabled services and/or devices (good lookup citizens). To
+be a good lookup citizen, a program must interoperate with other good
+lookup citizens and behave in a way that doesn't cause trouble for the
+rest of the networks, such as swamping a network with too much traffic.
+The rules of good citizenship are detailed in the Jini technology
+specifications and are, to a lesser extent, codified in the LDJ Kit.
+<p>
+The LDJ Kit software consists of a test framework and a set of tests that
+verify that a Jini technology-enabled program meets certain aspects of the core
+specifications. Note that a single LDJ Kit installation can test clients,
+services, and lookup services.<p>
+<hr>
+
+<h2>Verify that your path environment variable is set up properly</h2>
+<blockquote> 
+    <p>
+    Make sure that the 
+    Java(TM) 2 SDK, Standard Edition
+    executable files are accessible from your executable path
+    environment variable. You can test to ensure that you have a
+    version of the Java 2 SDK installed that is v1.2.2 or later and that
+    your executable path is set up properly by typing:
+    <pre>
+	java -version
+    </pre>
+    <p>
+    You may wish to use a platform on which the LDJ Kit has been tested, and
+    which are listed at
+    <a href="http://java.sun.com/developer/products/jini/tested.html">
+    http://java.sun.com/developer/products/jini/tested.html</a>.
+</blockquote> 
+
+<h2>Install the Jini Technology Lookup, Discovery, and Join Compatibility Kit
+v1.0</h2>
+<blockquote> 
+    <p>
+    Once you have downloaded the Jini Technology Lookup, Discovery, and Join
+    Compatibility Kit v1.0 you will need to extract it. For example,
+    <p>
+    On a UNIX platform, the following commands
+    <pre>
+	% mkdir /files
+	% cp jinildj-1_0.zip /files
+	% cd /files 
+	% jar xvf jinildj-1_0.zip
+    </pre>
+	would result in the creation of the
+	<code>/files/jinildj1_0</code> directory, which will be referred
+	to as the LDJ Kit installation directory.
+	<p>
+    On the Microsoft Windows platform, the following commands
+    <pre>
+
+	C:\&gt; mkdir C:\files
+	C:\&gt; copy jinildj-1_0.zip  C:\files
+	C:\&gt; cd C:\files 
+	C:\&gt; jar xvf jinildj-1_0.zip
+    </pre>
+	would result in the creation of the
+	<code>C:\files\jinildj1_0</code> directory, which will be
+	referred to as the LDJ Kit installation directory.
+</blockquote>
+
+You are now ready to run the test harness in the LDJ Kit.  For instructions on how
+to configure and run the LDJ Kit test suite, take a look at <i><a
+href="running.html">running.html</i></a>. Also, it may be helpful
+to read the <i><a href="release-notes.html">release notes</i></a>.
+<p>
+<hr>
+
+Copyright 2005, Sun Microsystems, Inc.<br>
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+Apache License, Version 2.0</a>.
+
+</body>
+</html>

Propchange: river/tck/doc/installation.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/passing.html
URL: http://svn.apache.org/viewvc/river/tck/doc/passing.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/passing.html (added)
+++ river/tck/doc/passing.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,105 @@
+<!--
+ !
+ ! Copyright 2005, Sun Microsystems, Inc.
+ ! Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+ ! Apache License, Version 2.0</a>.
+ !
+ !-->
+<html>
+
+<head>
+<title>Passing the LDJ Kit</title>
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1><CENTER>
+  Passing the Jini(TM) Technology Lookup, Discovery, and Join Compatibility Kit<BR>
+v1.0
+</CENTER></h1>
+
+<hr>
+<h2>
+  1&nbsp;&nbsp;&nbsp;Overview
+</h2>
+<p>
+  The Jini(TM) Technology Lookup, Discovery, and Join Compatibility Kit (LDJ Kit) validates whether you have conformed to the Jini technology specifications. This document describes what it means to &#34;pass the LDJ Kit&#34;.
+</p>
+<p>
+  You can use the LDJ Kit in two ways: <code>verifying</code> and <code>unofficial.</code> A verifying run can be used to verify conformance of your program to the tests of the LDJ Kit. An unofficial use is one that uses the LDJ Kit harness in a way that is not sufficient for these purposes, although you may find it helpful for other purposes. For example, you might find that your program initially fails a particular test. You can use unofficial executions of the LDJ Kit to debug the problem by running only that test instead of the entire test suite. When you have fixed things, you will then need a verifying run to confirm your program's conformance.
+</p>
+<p>
+  This document defines what you must do to create a verifying run of the LDJ Kit for a single program. Anything you do in the execution of an LDJ Kit run that does not conform to this document makes that run an unofficial run. Each separate program must independently satisfy the requirements expressed in this document.
+</p>
+<p>
+  The LDJ Kit consists of several parts:
+</p>
+<ul>
+  <li class="SmartList1">This document.
+  <li class="SmartList1">An LDJ Kit program, written in the Java(TM) programming language, that performs several tests on your program. Which tests are run depends on your program's category (client, service, or lookup service).
+  <li class="SmartList1">Documentation for how to run the LDJ Kit, interpret its results, and adapt it to your program more effectively should you choose to do so.
+  <li class="SmartList1">The source to the LDJ Kit harness and tests, and the specifications for these components. These are included for your information only.
+</ul>
+<p>
+  When you receive the LDJ Kit you will get all these parts in a single file. After extracting the LDJ Kit on your system you can use the included instructions to run the LDJ Kit.
+</p>
+<h2>
+  2&nbsp;&nbsp;&nbsp;Verifying Runs
+</h2>
+<p>
+  The LDJ Kit contains a test harness and a set of tests that are run using the harness. A verifying run is made up of one or more separate <em>official runs</em> of the LDJ Kit. An official run of the LDJ Kit is a single execution of the harness that meets certain requirements.
+</p>
+<h3>
+  2.1&nbsp;&nbsp;&nbsp;Official Run Requirements
+</h3>
+<p>
+  An official run of the LDJ Kit is a single execution of the harness that meets the following requirements:
+</p>
+    <ol type="1">
+      <li class="SmartList3" value="1">You must use an unmodified version of the LDJ Kit as it is shipped. For example, you must not use a version of the LDJ Kit that has been built from the source shipped to you with the LDJ Kit, whether or not that source has been modified from the original.
+      <li class="SmartList3" value="2">You must not have modified any files in the installation directory of the LDJ Kit. For example, if you want to use a configuration properties file different from the default shipped with the LDJ Kit, you must make a copy of that file, modify the copy, and tell the LDJ Kit harness to use your modified copy.
+      <li class="SmartList3" value="3">All tests relevant to your program category must be executed. You must select the correct category for your program, depending upon its behavior. For example, if your program is a Jini technology-enabled service (<em>Jini service</em>) that also acts as a Jini technology-enabled client (<em>Jini client</em>), then you'll need to run both the client and service tests against your program to be considered conformant. If your program is a Jini lookup service that also acts as a Jini service (registers in other lookups), then you'll need to run both the service and lookup tests against your program. You must therefore run the LDJ Kit with a <code>-categories</code> option or a <code>com.sun.jini.compat.categories</code> property that includes all relevant program categories and no irrelevant program categories.
+      <li class="SmartList3" value="4">The following option must not be used: <code>-tests</code>.
+      <li class="SmartList3" value="5">The following properties must have their default values in an official run: <code>com.sun.jini.compat.debugLevel</code>, <code>com.sun.jini.compat.unofficialQuietTime</code>.
+      <li class="SmartList3" value="6">You must run the LDJ Kit using a Java 2 SDK Standard Edition (J2SE(TM)) or Enterprise Edition (J2EE(TM)) virtual machine for the Java platform. The <code>java</code> executable that the LDJ Kit harness will get by invoking the method <code>Runtime.exec</code> with a string starting with <code>"java"</code> must also provide a J2SE or J2EE virtual machine.
+      <li class="SmartList3" value="7">Your program must be run in a network that is a reasonable example of at least one of your intended deployment configurations.
+    </ol>
+<p>
+  You have many options on how you execute an official run. Any circumstance that causes a failure in the LDJ Kit harness or any of its tests is your responsibility to fix. Among the options you have are:
+</p>
+    <ol type="1">
+      <li class="SmartList3" value="1">You may run your program anywhere in the network.
+      <li class="SmartList3" value="2">You may run the LDJ Kit on any system in your network.
+      <li class="SmartList3" value="3">You may run the LDJ Kit using any J2SE or J2EE virtual machine, but if you encounter problems, you should try one of the platforms on which we have verified the correctness of the LDJ Kit, listed at
+<a href="http://java.sun.com/developer/products/jini/tested.html">
+http://java.sun.com/developer/products/jini/tested.html</a>.
+      <li class="SmartList3" value="4">Your network may be of any quality. Clearly a less reliable network increases the likelihood of some failures.
+      <li class="SmartList3" value="5">You may write an implementation of the appropriate Admin interfaces (described in <em><a href="writing-admin.html">Implementing the Jini Technology Lookup, Discovery, and Join Compatibility Kit, v1.0 Admin Interface</a></em>) to automate your test runs.
+      <li class="SmartList3" value="6">You may adjust the property <code>com.sun.jini.compat.failureTime</code> to any length of time.
+      <li class="SmartList3" value="7">If your program is user configurable, only a single configuration is required to pass a verifying run.
+    </ol>
+<h3>
+  2.2&nbsp;&nbsp;&nbsp;Verifying Run
+</h3>
+<p>
+  A verifying run of the LDJ Kit consists of one or more official runs that satisfy the following requirements:
+</p>
+    <ol type="1">
+      <li class="SmartList3" value="1">Each individual test in the selected categories must <code>pass</code> (defined below) at least 66% of the time in the set of official runs. For example, if all tests in one run pass, you are at 100% <em>for each test</em>; if you make several test runs, <em>each test</em> must pass 66% of the time over the span of runs.
+      <li class="SmartList3" value="2">Your program implementation must not be modified between runs.
+      <li class="SmartList3" value="3">Any implementation of the <code>Admin</code> interfaces you use in the LDJ Kit must not be modified between runs.
+      <li class="SmartList3" value="4">Any external files relied upon by the test (such as properties and security files) must not be modified between runs.
+      <li class="SmartList3" value="5">The configuration of your program must not change between runs. For example, if your service is a program, the command line used to execute it must be the same in all official runs.
+      <li class="SmartList3" value="6">There must be no additional official runs of the LDJ Kit against your program between the start of the first official run and the end of the final official run. For example, a set of consecutive official runs would satisfy this requirement.
+    </ol>
+<p>
+  A test is passed if it is executed in an official run and the test reports its status as <code>Passed</code>.
+</p>
+
+<hr>
+
+Copyright 2005, Sun Microsystems, Inc.<br>
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+Apache License, Version 2.0</a>.
+
+</body>
+</html>

Propchange: river/tck/doc/passing.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: river/tck/doc/release-notes.html
URL: http://svn.apache.org/viewvc/river/tck/doc/release-notes.html?rev=1234278&view=auto
==============================================================================
--- river/tck/doc/release-notes.html (added)
+++ river/tck/doc/release-notes.html Sat Jan 21 07:28:27 2012
@@ -0,0 +1,54 @@
+<!--
+ ! 
+ ! Copyright 2005, Sun Microsystems, Inc.
+ ! Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+ ! Apache License, Version 2.0</a>.
+ ! 
+ !-->
+<html>
+<body text="#000000" bgcolor="#ffffff" link="#9b37cc"
+      vlink="#cc1877" alink="#ffffff">
+
+
+<title>Jini(TM) LDJ Kit Release Notes</title>
+
+<center>
+<h1>Jini(TM) Technology Lookup, Discovery, and Join
+Compatibility Kit Release Notes<BR>
+v1.0</h1>
+</center>
+
+<hr>
+
+<h2>Known issues</h2>
+<ul>	<li>The Jini(TM) Technology Lookup, Discovery, and Join
+	Compatibility Kit (LDJ Kit) must be run either 
+	on a host that is not running any
+	other Jini technology-enabled services, clients, or lookup
+	services; <i>or</i> on a system that is running only the
+	service, client, or lookup service that you are testing.
+	<p>
+	<li>If the test harness is interrupted (for example, by a 	
+	<code>CTRL-c</code>) before it can complete, you may have to
+	remove a few files and directories yourself:
+	<ul>
+	<li>Stop <code>rmid</code>, remove its <code>log</code> directory, 
+	and restart <code>rmid</code>.
+	<li>Remove files that did not come with the LDJ Kit from the
+	<code>jinildj1_0/lib/dl/</code> directory. The only files that
+	should remain are <code>compat-dl.jar</code> and
+	<code>compat-lus-dl.jar</code>.
+	<li>If the service you were testing used the file system to
+	persist its state, you'll need to remove the appropriate
+	persistence directories and files.
+	</ul>
+</ul>
+<p>
+<hr>
+
+Copyright 2005, Sun Microsystems, Inc.<br>
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">
+Apache License, Version 2.0</a>.
+
+</body>
+</html>

Propchange: river/tck/doc/release-notes.html
------------------------------------------------------------------------------
    svn:eol-style = native