You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by bu...@apache.org on 2010/11/06 00:23:47 UTC
svn commit: r778766 - /websites/staging/river/trunk/content/
Author: buildbot
Date: Fri Nov 5 23:23:46 2010
New Revision: 778766
URL: http://svn.apache.org/viewvc?rev=778766&view=rev
Log:
Staging update by buildbot
Modified:
websites/staging/river/trunk/content/development-process.html
websites/staging/river/trunk/content/documentation.html
websites/staging/river/trunk/content/downloads.html
websites/staging/river/trunk/content/found-a-bug.html
websites/staging/river/trunk/content/get-involved.html
websites/staging/river/trunk/content/index.html
websites/staging/river/trunk/content/mailing-lists.html
websites/staging/river/trunk/content/sidenav-quick-links.html
websites/staging/river/trunk/content/sidenav.html
websites/staging/river/trunk/content/source-code.html
websites/staging/river/trunk/content/user-guide-basic-river-services.html
websites/staging/river/trunk/content/user-guide-river-jar-artifacts.html
Modified: websites/staging/river/trunk/content/development-process.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/development-process.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/development-process.html (original)
+++ websites/staging/river/trunk/content/development-process.html Fri Nov 5 23:23:46 2010
@@ -39,11 +39,11 @@ The preferred place of discussion on iss
<ul>
<li>
<p>for public API changes:
-[RTC|http://apache.org/foundation/glossary.html#ReviewThenCommit] These changes have potentially broad effects on developers and users, and therefore will require a code review and vote. Since some of these changes will affect the API docs ('specs'), everyone within the Jini/River community is encouraged to review and vote. The Committer votes are binding, but the sentiment of the entire community will be strongly considered.</p>
+<a href="http://apache.org/foundation/glossary.html#ReviewThenCommit">RTC</a> These changes have potentially broad effects on developers and users, and therefore will require a code review and vote. Since some of these changes will affect the API docs ('specs'), everyone within the Jini/River community is encouraged to review and vote. The Committer votes are binding, but the sentiment of the entire community will be strongly considered.</p>
</li>
<li>
<p>for all other changes:
-[CTR|http://apache.org/foundation/glossary.html#CommitThenReview] Although CTR is what is specified, developers should feel comfortable requesting the list for peer review before committing.</p>
+<a href="http://apache.org/foundation/glossary.html#CommitThenReview">CTR</a> Although CTR is what is specified, developers should feel comfortable requesting the list for peer review before committing.</p>
</li>
</ul>
<h3 id="testing">Testing</h3>
Modified: websites/staging/river/trunk/content/documentation.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/documentation.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/documentation.html (original)
+++ websites/staging/river/trunk/content/documentation.html Fri Nov 5 23:23:46 2010
@@ -19,29 +19,25 @@
<div id="page" class="container_16">
<div class="clear"></div>
<div id="content" class="grid_16"><div class="section-content"><h1 id="apache_river_documentation">Apache River Documentation</h1>
-<p>The original Jini documentation (including the formal specifications) can be found [here|http://incubator.apache.org/river/doc/index.html]. For more general help and information please see the list of topics below.</p>
+<p>The original Jini documentation (including the formal specifications) can be found <a href="http://incubator.apache.org/river/doc/index.html">here</a>. For more general help and information please see the list of topics below.</p>
<table>
<thead>
<tr>
<th />
<th>Document</th>
-<th />
</tr>
</thead>
<tbody>
<tr>
-<td>[Glossary</td>
-<td>User Guide - Glossary ]</td>
+<td><a href="User Guide - Glossary">Glossary</a></td>
<td>A definition of a few of the common terms when using Jini/River</td>
</tr>
<tr>
-<td>[River Artifacts</td>
-<td>User Guide - River JAR Artifacts ]</td>
+<td><a href="User Guide - River JAR Artifacts">River Artifacts</a></td>
<td>An extract from the developer list discussing the history behind River's JAR artifacts</td>
</tr>
<tr>
-<td>[Socket Factories</td>
-<td>User Guide - SocketFactories]</td>
+<td><a href="User Guide - SocketFactories">Socket Factories</a></td>
<td>A note on the correct use of SocketFactories in EndPoints</td>
</tr>
</tbody>
Modified: websites/staging/river/trunk/content/downloads.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/downloads.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/downloads.html (original)
+++ websites/staging/river/trunk/content/downloads.html Fri Nov 5 23:23:46 2010
@@ -20,14 +20,14 @@
<div class="clear"></div>
<div id="content" class="grid_16"><div class="section-content"><h1 id="apache_river_downloads">Apache River Downloads</h1>
<p>Use the links below to download Apache River releases from one of our mirrors. You should verify the integrity of the files using the signatures and checksums available from this page.</p>
-<p>Apache River releases are available under the [Apache License, Version 2.0|http://www.apache.org/licenses/LICENSE-2.0]. See the NOTICE.txt file contained in each release artifact for applicable copyright attribution notices.</p>
+<p>Apache River releases are available under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>. See the NOTICE.txt file contained in each release artifact for applicable copyright attribution notices.</p>
<h2 id="apache_river_v212_incubating">Apache River v2.1.2 (incubating)</h2>
<ul>
-<li>Source code: [apache-river-2.1.2-incubating-src.zip|http://www.apache.org/dyn/closer.cgi/incubator/river/source/2.1.2/apache-river-2.1.2-incubating-src.zip] ([PGP|http://www.apache.org/dist/incubator/river/source/2.1.2/apache-river-2.1.2-incubating-src.zip.asc], [SHA1|http://www.apache.org/dist/incubator/river/source/2.1.2/apache-river-2.1.2-incubating-src.zip.sha])</li>
-<li>Binary: [apache-river-2.1.2-incubating-bin.zip|http://www.apache.org/dyn/closer.cgi/incubator/river/binaries/2.1.2/apache-river-2.1.2-incubating-bin.zip] ([PGP|http://www.apache.org/dist/incubator/river/binaries/2.1.2/apache-river-2.1.2-incubating-bin.zip.asc], [SHA1|http://www.apache.org/dist/incubator/river/binaries/2.1.2/apache-river-2.1.2-incubating-bin.zip.sha])</li>
+<li>Source code: <a href="http://www.apache.org/dyn/closer.cgi/incubator/river/source/2.1.2/apache-river-2.1.2-incubating-src.zip">apache-river-2.1.2-incubating-src.zip</a> (<a href="http://www.apache.org/dist/incubator/river/source/2.1.2/apache-river-2.1.2-incubating-src.zip.asc">PGP</a>, <a href="http://www.apache.org/dist/incubator/river/source/2.1.2/apache-river-2.1.2-incubating-src.zip.sha">SHA1</a>)</li>
+<li>Binary: <a href="http://www.apache.org/dyn/closer.cgi/incubator/river/binaries/2.1.2/apache-river-2.1.2-incubating-bin.zip">apache-river-2.1.2-incubating-bin.zip</a> (<a href="http://www.apache.org/dist/incubator/river/binaries/2.1.2/apache-river-2.1.2-incubating-bin.zip.asc">PGP</a>, <a href="http://www.apache.org/dist/incubator/river/binaries/2.1.2/apache-river-2.1.2-incubating-bin.zip.sha">SHA1</a>)</li>
</ul>
<h2 id="release_archive">Release Archive</h2>
-<p>Only current, recommended releases are available on www.apache.org and the mirror sites. Older releases, when available, can be obtained from the [archive site|http://archive.apache.org/dist/incubator/river/].</p>
+<p>Only current, recommended releases are available on www.apache.org and the mirror sites. Older releases, when available, can be obtained from the <a href="http://archive.apache.org/dist/incubator/river/">archive site</a>.</p>
<h2 id="nightly_snapshots">Nightly Snapshots</h2>
<p>Being worked on - none yet.</p>
<h2 id="pgp_signatures">PGP Signatures</h2>
@@ -47,7 +47,7 @@
% gpg --import KEYS
% gpg --verify filename.zip.asc
{code}</p>
-<p>We offer MD5 hashes as an alternative to validate the integrity of the downloaded files. A unix program called md5 or md5sum is included in many unix distributions. It is also available as part of [GNU Core Utilities package|http://www.gnu.org/software/coreutils].</p></div></div>
+<p>We offer MD5 hashes as an alternative to validate the integrity of the downloaded files. A unix program called md5 or md5sum is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/coreutils">GNU Core Utilities package</a>.</p></div></div>
<div class="clear"></div>
</div>
<div class="clear"></div>
Modified: websites/staging/river/trunk/content/found-a-bug.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/found-a-bug.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/found-a-bug.html (original)
+++ websites/staging/river/trunk/content/found-a-bug.html Fri Nov 5 23:23:46 2010
@@ -19,7 +19,7 @@
<div id="page" class="container_16">
<div class="clear"></div>
<div id="content" class="grid_16"><div class="section-content"><h2 id="found_a_bug">Found a Bug?</h2>
-<p>If you think you've found a problem with Apache River you can search JIRA, our issue-tracking system, to see if the problem has already been noted (visit [JIRA|http://issues.apache.org/jira/browse/RIVER]). If the issue is not listed there, you can add a new JIRA issue describing it, please include detailed steps to reproduce the problem. Often it is best to raise an issue not yet listed in JIRA first on the River Developer mailing list (see [Mailing Lists]) before adding it directly in JIRA.</p>
+<p>If you think you've found a problem with Apache River you can search JIRA, our issue-tracking system, to see if the problem has already been noted (visit <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>). If the issue is not listed there, you can add a new JIRA issue describing it, please include detailed steps to reproduce the problem. Often it is best to raise an issue not yet listed in JIRA first on the River Developer mailing list (see [Mailing Lists]) before adding it directly in JIRA.</p>
<p>If you have a fix for the issue, you can generate a patch file to send the fix to us. You need to check out the current source code from Subversion, make the necessary changes, and then do a full build. And, of course, confirm that the problem is actually fixed. Then, go to the base directory of your RIVER checkout, and run a command like {{svn diff > fix-for-my-bug.patch}} to generate a patch file.</p>
<p>To submit a patch, create an issue in JIRA that describes the problem, and add your patch file as an attachment. Please include detailed steps to reproduce the problem in the issue description, and a test case in the patch where possible.</p>
<p>Thanks for interest, and working with us to improve Apache River!</p></div></div>
Modified: websites/staging/river/trunk/content/get-involved.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/get-involved.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/get-involved.html (original)
+++ websites/staging/river/trunk/content/get-involved.html Fri Nov 5 23:23:46 2010
@@ -32,8 +32,8 @@
<h3 id="how_do_i_contribute">How do I Contribute?</h3>
<ul>
<li>To discuss Apache River topics check out the [mailing lists].</li>
-<li>Bugs and other issues can be posted in the [RIVER|http://issues.apache.org/jira/browse/RIVER] issue tracker.</li>
-<li>The [River wiki|http://wiki.apache.org/river/] is open for anyone to contribute related documentation.</li>
+<li>Bugs and other issues can be posted in the <a href="http://issues.apache.org/jira/browse/RIVER">RIVER</a> issue tracker.</li>
+<li>The <a href="http://wiki.apache.org/river/">River wiki</a> is open for anyone to contribute related documentation.</li>
</ul></div></div>
<div class="clear"></div>
</div>
Modified: websites/staging/river/trunk/content/index.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/index.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/index.html (original)
+++ websites/staging/river/trunk/content/index.html Fri Nov 5 23:23:46 2010
@@ -21,15 +21,15 @@
<div id="content" class="grid_16"><div class="section-content"><h2 id="welcome_to_apache_river">Welcome to Apache River</h2>
<p>Welcome to Apache River, a project furthering the development and advancement of Jini technology.</p>
<p>Jini is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems consisting of federations of services and clients. Jini technology can be used to build adaptive network systems that are scalable, evolvable and flexible as typically required in dynamic computing environments.</p>
-<p>Apache River is an effort undergoing incubation at [The Apache Software Foundation|http://www.apache.org/] (ASF), sponsored by the [Apache Incubator|http://incubator.apache.org/] PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.</p>
+<p>Apache River is an effort undergoing incubation at <a href="http://www.apache.org/">The Apache Software Foundation</a> (ASF), sponsored by the <a href="http://incubator.apache.org/">Apache Incubator</a> PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.</p>
<h2 id="news">News</h2>
<p>{blog-posts:5} </p>
<h2 id="resources">Resources</h2>
<ul>
-<li>Apache Incubator [Proposal for the River project | http://wiki.apache.org/incubator/RiverProposal]</li>
-<li>[Jini.org | http://www.jini.org]</li>
-<li>[Jini project area on Java.net | http://jini.dev.java.net]</li>
-<li>Jan Newmarch's [Guide to Jini Technologies | http://jan.newmarch.name/java/jini/tutorial/Jini.xml]</li>
+<li>Apache Incubator <a href="http://wiki.apache.org/incubator/RiverProposal">Proposal for the River project </a></li>
+<li><a href="http://www.jini.org">Jini.org </a></li>
+<li><a href="http://jini.dev.java.net">Jini project area on Java.net </a></li>
+<li>Jan Newmarch's <a href="http://jan.newmarch.name/java/jini/tutorial/Jini.xml">Guide to Jini Technologies </a></li>
</ul></div></div>
<div class="clear"></div>
</div>
Modified: websites/staging/river/trunk/content/mailing-lists.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/mailing-lists.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/mailing-lists.html (original)
+++ websites/staging/river/trunk/content/mailing-lists.html Fri Nov 5 23:23:46 2010
@@ -28,34 +28,22 @@
<th />
<th>Subscribe</th>
<th />
-<th>Unsubscribe</th>
-<th />
-<th>Post</th>
-<th />
</tr>
</thead>
<tbody>
<tr>
<td>River User List</td>
-<td>[river-user-subscribe</td>
-<td>mailto:river-user-subscribe@incubator.apache.org]</td>
-<td>[river-user-unsubscribe</td>
-<td>mailto:river-user-unsubscribe@incubator.apache.org]</td>
-<td>[river-user</td>
-<td>mailto:river-user@incubator.apache.org]</td>
-<td>[mail-archives.apache.org</td>
-<td>http://mail-archives.apache.org/mod_mbox/incubator-river-user/]</td>
+<td><a href="mailto:river-user-subscribe@incubator.apache.org">river-user-subscribe</a></td>
+<td><a href="mailto:river-user-unsubscribe@incubator.apache.org">river-user-unsubscribe</a></td>
+<td><a href="mailto:river-user@incubator.apache.org">river-user</a></td>
+<td><a href="http://mail-archives.apache.org/mod_mbox/incubator-river-user/">mail-archives.apache.org</a></td>
</tr>
<tr>
<td>River Commits List</td>
-<td>[river-commits-subscribe</td>
-<td>mailto:river-commits-subscribe@incubator.apache.org]</td>
-<td>[river-commits-unsubscribe</td>
-<td>mailto:river-commits-unsubscribe@incubator.apache.org]</td>
-<td>[river-commits</td>
-<td>mailto:river-commits@incubator.apache.org]</td>
-<td>[mail-archives.apache.org</td>
-<td>http://mail-archives.apache.org/mod_mbox/incubator-river-commits/]</td>
+<td><a href="mailto:river-commits-subscribe@incubator.apache.org">river-commits-subscribe</a></td>
+<td><a href="mailto:river-commits-unsubscribe@incubator.apache.org">river-commits-unsubscribe</a></td>
+<td><a href="mailto:river-commits@incubator.apache.org">river-commits</a></td>
+<td><a href="http://mail-archives.apache.org/mod_mbox/incubator-river-commits/">mail-archives.apache.org</a></td>
</tr>
</tbody>
</table></div></div>
Modified: websites/staging/river/trunk/content/sidenav-quick-links.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/sidenav-quick-links.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/sidenav-quick-links.html (original)
+++ websites/staging/river/trunk/content/sidenav-quick-links.html Fri Nov 5 23:23:46 2010
@@ -19,9 +19,9 @@
<div id="page" class="container_16">
<div class="clear"></div>
<div id="content" class="grid_16"><div class="section-content"><ul>
-<li>[Home|Index] </li>
+<li><a href="Index">Home</a> </li>
<li>[License]</li>
-<li>[ASF|http://apache.org]</li>
+<li><a href="http://apache.org">ASF</a></li>
<li>[Downloads]</li>
<li>[Site Map]</li>
</ul></div></div>
Modified: websites/staging/river/trunk/content/sidenav.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/sidenav.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/sidenav.html (original)
+++ websites/staging/river/trunk/content/sidenav.html Fri Nov 5 23:23:46 2010
@@ -34,8 +34,8 @@
<li>[Javadoc]</li>
<li>[Source Code]</li>
<li>[Development Process]</li>
-<li>[Issue Tracker|https://issues.apache.org/jira/browse/RIVER]</li>
-<li>[Wiki|http://wiki.apache.org/river/]</li>
+<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
+<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
<h3 id="search">Search</h3>
<p>{html}
Modified: websites/staging/river/trunk/content/source-code.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/source-code.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/source-code.html (original)
+++ websites/staging/river/trunk/content/source-code.html Fri Nov 5 23:23:46 2010
@@ -19,7 +19,7 @@
<div id="page" class="container_16">
<div class="clear"></div>
<div id="content" class="grid_16"><div class="section-content"><h1 id="river_source_code">River source code</h1>
-<p>River uses [Subversion|http://subversion.tigris.org/] to manage its source code. Instructions on Subversion use can be found [here|http://svnbook.red-bean.com].</p>
+<p>River uses <a href="http://subversion.tigris.org/">Subversion</a> to manage its source code. Instructions on Subversion use can be found <a href="http://svnbook.red-bean.com">here</a>.</p>
<p>The source code for the various deliverables of Apache River can be freely browsed at [http://svn.apache.org/viewvc/incubator/river/]. </p>
<h2 id="anonymous_access">Anonymous access</h2>
<p>The Apache River source can be checked out anonymously with this command (for the jtsk deliverable):</p>
@@ -41,7 +41,7 @@ http-proxy-host = your.proxy.name
http-proxy-port = 3128
{noformat}</p>
<h2 id="submitting_a_patch">Submitting a Patch</h2>
-<p>If you make changes to River, and would like to contribute the to the project, you should create a patch and post it to the [River JIRA issue tracker|http://issues.apache.org/jira/browse/RIVER]. To create a patch, simply execute the following command:</p>
+<p>If you make changes to River, and would like to contribute the to the project, you should create a patch and post it to the <a href="http://issues.apache.org/jira/browse/RIVER">River JIRA issue tracker</a>. To create a patch, simply execute the following command:</p>
<p>{noformat}
svn diff > your-changes.patch
{noformat}</p>
Modified: websites/staging/river/trunk/content/user-guide-basic-river-services.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/user-guide-basic-river-services.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/user-guide-basic-river-services.html (original)
+++ websites/staging/river/trunk/content/user-guide-basic-river-services.html Fri Nov 5 23:23:46 2010
@@ -51,7 +51,7 @@ System.setSecurityManager(new RMISecurit
<h2 id="starting_the_http_server">Starting the HTTP server</h2>
<h3 id="what__wait_why_do_i_need_to_do_that">What? Wait, why do I need to do that?</h3>
<p>When services get marshalled for sending over the wire, the first part of their stream is the codebase URL. This URL tells the downloading JVM where to load the supporting JARs from. Often (although not always) in the River/Jini world this code base harks back to some HTTP server. There is a simple HTPP server packaged inside River which can be used for this. That's what we're going to start.</p>
-<p>See [3.2 How codebase is used in Java RMI|http://download.oracle.com/javase/1.5.0/docs/guide/rmi/codebase.html] for more details.</p>
+<p>See <a href="http://download.oracle.com/javase/1.5.0/docs/guide/rmi/codebase.html">3.2 How codebase is used in Java RMI</a> for more details.</p>
<h3 id="instructions">Instructions</h3>
<h1 id="change_to_directory_to_river_homeexampleshello">Change to directory to {{$RIVER_HOME/examples/hello/}}</h1>
<h1 id="execute_the_script_scriptshttpdbat">Execute the script; {{scripts/httpd.bat}}</h1>
@@ -77,7 +77,7 @@ StreamServiceRegistrar sr = ll.getStream
System.out.println("Service Registrar: "+sr.getServiceID());
{code}</p>
<p>Assuming you don't get a {{NullPointerException}} and you do get a service ID written out, then your Lookup Service is running fine.</p>
-<p>The {{LookupLocator}} takes a String representing a "jini URL". This jini URL is made up from the Strings "{{jini://}}" a hostname and (optionally) "{{:}}" and a port number. 4160 is the default port and is specified in the Lookup Service configuration file. The scripts in the {{examples/hello}} directory will use the default port unless you have changed it. See [DJ.5.5 Address and Port Mappings for TCP and Multicast UDP|http://incubator.apache.org/river/doc/specs/html/discovery-spec.html] for more details.</p>
+<p>The {{LookupLocator}} takes a String representing a "jini URL". This jini URL is made up from the Strings "{{jini://}}" a hostname and (optionally) "{{:}}" and a port number. 4160 is the default port and is specified in the Lookup Service configuration file. The scripts in the {{examples/hello}} directory will use the default port unless you have changed it. See <a href="http://incubator.apache.org/river/doc/specs/html/discovery-spec.html">DJ.5.5 Address and Port Mappings for TCP and Multicast UDP</a> for more details.</p>
<h4 id="multicast">Multicast</h4>
<p>If we know only that "some lookup services are on the subnet somewhere" then we can use multicast to find them.</p>
<p>{code:title=Multicast|borderStyle=solid}
@@ -101,14 +101,14 @@ for(ServiceItem si : sis) {
<h1 id="change_directory_to_river_homeexampleshello_1">Change directory to $RIVER_HOME/examples/hello</h1>
<h1 id="execute_the_script_scriptsjrmp-outrigger-groupbat">Execute the script {{scripts/jrmp-outrigger-group.bat}}</h1>
<h3 id="testing_it_2">Testing it</h3>
-<p>{code:title=Finding A Javaspace with a ServiceRegistrar|borderStyle=solid}
-ServiceTemplate template = new ServiceTemplate(null, new Class[] { JavaSpace.class }, new Entry[0]);</p>
+<p>{code:title=Finding A Javaspace with a ServiceRegistrar](borderStyle=solid}
+ServiceTemplate template = new ServiceTemplate(null, new Class[) { JavaSpace.class }, new Entry[0]);</p>
<p>ServiceMatches sms = sr.lookup(template, 10);
for(ServiceItem si : sms.items) {
System.out.println("Found: "+si);
}
{code}</p>
-<p>{code:title=Finding A Javaspace with a ServiceDiscoveryManager|borderStyle=solid}
+<p>{code:title=Finding A Javaspace with a ServiceDiscoveryManager](borderStyle=solid}
ServiceItem si = sdm.lookup(template, null);
System.out.println("Java Space: "+(JavaSpace)si.service);
{code}</p>
@@ -122,7 +122,7 @@ System.out.println("Java Space: "+(JavaS
<h3 id="testing_it_3">Testing it</h3>
<p>Testing it is done in the same way as for the Java Space. However, the constructor of the {{ServiceTemplate}} changes.</p>
<p>{code:title=Transaction Manager ServiceTemplate|borderStyle=solid}
-ServiceTemplate template = new ServiceTemplate(null, new Class[] { TransactionManager.class }, new Entry[0]);
+ServiceTemplate template = new ServiceTemplate(null, new Class[) { TransactionManager.class }, new Entry[0]);
{code}</p></div></div>
<div class="clear"></div>
</div>
Modified: websites/staging/river/trunk/content/user-guide-river-jar-artifacts.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/user-guide-river-jar-artifacts.html?rev=778766&r1=778765&r2=778766&view=diff
==============================================================================
--- websites/staging/river/trunk/content/user-guide-river-jar-artifacts.html (original)
+++ websites/staging/river/trunk/content/user-guide-river-jar-artifacts.html Fri Nov 5 23:23:46 2010
@@ -19,7 +19,7 @@
<div id="page" class="container_16">
<div class="clear"></div>
<div id="content" class="grid_16"><div class="section-content"><h1 id="use_guide_-_river_jar_artifacts">Use Guide - River JAR Artifacts</h1>
-<p>The following is an extract from Brian Murphy's [post|http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201008.mbox/%3cAANLkTi=bfA5q-n_5f-ft1Pv+VKt2ZV2MUEbX2GN4+TTD@mail.gmail.com%3e] on the developer mailing list highlight some of the history behind the River/Jini JAR artifacts.</p>
+<p>The following is an extract from Brian Murphy's <a href="http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201008.mbox/%3cAANLkTi=bfA5q-n_5f-ft1Pv+VKt2ZV2MUEbX2GN4+TTD@mail.gmail.com%3e">post</a> on the developer mailing list highlight some of the history behind the River/Jini JAR artifacts.</p>
<p>{quote}For those who might be wondering about artifacts like jini-core.jar, jini-ext.jar, sun-util.jar, etc., although there have been previous postings discussing how they are no longer needed, it might help some of the new folks on the list to hear a repeat of the history of those artifacts; and why they should not be used, and why they should probably be removed from the build.</p>
<p>Back in the old jini 2.x release time frame, there was quite a bit of time and thought put into how the distribution should be re-packaged to address deployment issues; for example, better modularity, supporting overlays when upgrading, etc. That work resulted in the current artifact structure we now see; jsk-platform/jsk-lib/jsk-resources/jsk-dl/<service>/<service>-dl.</p>
<p>But because the team did not want to break existing deployments that relied on the old jar structure, they decided to also include the old artifacts in the release; along with a detailed release note explaining the new philosophy and encouraging folks to move to the new model, and be prepared for the removal of those old jar files down the road. Unfortunately, due to unforeseen events, the removal of the old unnecessary jar files never occurred, and people seem to still be using them (at least, based on postings on the various user lists out there).