[cweb-CVS] bigdata build.xml,1.1,1.2

[Bryan T. <tho...@us...>]

Update of /cvsroot/cweb/bigdata
In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv18893

Modified Files:
	build.xml 
Log Message:
more work on jini support.

Index: build.xml
===================================================================
RCS file: /cvsroot/cweb/bigdata/build.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** build.xml	17 Mar 2007 23:14:59 -0000	1.1
--- build.xml	18 Mar 2007 22:29:43 -0000	1.2
***************
*** 72,75 ****
--- 72,79 ----
  	themselves are available for download (only .class files are downloaded, NOT
  	JARs).
+ 
+ 		cd /home/groups/c/cw/cweb/maven-repository/bigdata/jars
+ 			
+ 		/usr/java/j2sdk1.4.2_05/bin/jar xf bigdata.jar
  	
  	Finally, the code that will expose services with downloadable code MUST set
***************
*** 96,102 ****
--- 100,124 ----
  	for some (very good) guidence in debugging jini services.
  
+ 	Note: You may have to restart jini locally in order to force download of 
+ 	updated classes from the codebase!
+ 
  	See http://archives.java.sun.com/cgi-bin/wa?A2=ind0512&L=jini-users&P=R391&I=-3
  	for instructions on setting up an "download jar" (dljar) ANT task that can make
  	life much simpler (one supposes).
+ 
+     See http://archives.java.sun.com/cgi-bin/wa?A2=ind0311&L=jini-users&F=&S=&P=7182
+         for a description of policy files and
+         http://www.dancres.org/cottage/jini-start-examples-2_1.zip for the
+         policy files described.
+ 	
+ 	See http://jan.newmarch.name/java/jini/tutorial/Ant.xml for a description of
+ 	one (simple) approach to using ant for jini projects (it does not use the
+ 	dljar ant task but explicitly enumerates what goes where).
+ 	
+ 	See http://jan.newmarch.name/java/jini/tutorial/TroubleShooting.xml#RMI%20Stubs
+ 	for common errors when using RMI stubs.
+ 	
+ 	See https://java.sun.com/products/jini/2.1/doc/api/com/sun/jini/example/browser/package-summary.html
+ 	for the dirty on the jini Service Browser.
  	
  	@todo you need to install the client and server deployments on machines