Index of /pub/dods/DODS-Java-1.0/

NameLast ModifiedSize
UpParent Directory
Filedods.Binary.jar2008-05-23 23:20 364k
Filedods.Combined.jar2008-05-23 23:20 5444k
Filedods.Doc.jar2008-05-23 23:20 708k
Filedods.jar2008-05-23 23:20 388k
Filedods.Src.jar2008-05-23 23:20 4016k
Filedods.v_1_0.Binary.jar2008-05-23 23:20 360k
Filedods.v_1_0.Combined.jar2008-05-23 23:20 5428k
Filedods.v_1_0.Doc.jar2008-05-23 23:20 704k
Filedods.v_1_0.jar2008-05-23 23:20 384k
Filedods.v_1_0.Src.jar2008-05-23 23:20 4004k
Filedods.v_1_0_1.Binary.jar2008-05-23 23:20 360k
Filedods.v_1_0_1.Combined.jar2008-05-23 23:20 5428k
Filedods.v_1_0_1.Doc.jar2008-05-23 23:20 704k
Filedods.v_1_0_1.jar2008-05-23 23:20 384k
Filedods.v_1_0_1.Src.jar2008-05-23 23:20 4004k
Filedods.v_1_0_2.Binary.jar2008-05-23 23:20 364k
Filedods.v_1_0_2.Combined.jar2008-05-23 23:20 5444k
Filedods.v_1_0_2.Doc.jar2008-05-23 23:20 708k
Filedods.v_1_0_2.jar2008-05-23 23:20 388k
Filedods.v_1_0_2.Src.jar2008-05-23 23:20 4016k
README -- Java-DODS Release 1.0.2 The files located here are organized as follows: ---- dods.v_1_0_2.Doc.jar -- Contains all of the javadoc generated html files. ---- dods.v_1_0_2.Binary.jar -- This is the binary distribution containing the .class files of the current beta release of the code along with an example DODS.ini file which is useful if you are building a server. To use this file (dods.Beta_1_0.bin.jar): 1) Unjar it. It will make a directory called Java-DODS. 2) In the subdirectory Java-DODS/lib there should be the a file named "dods.jar". Place this file explicitly on your CLASSPATH if you wish to use it as the binary for the Java-DODS code. 3) If you are running or building a server, you should get the documentation bundle and read the section on dods.servlet.DODSServlet for instructions on how to get the servlet set up with the .ini files. Examples of .ini files can be found in the Java-DODS/ini directory in this bundle. ---- dods.v_1_0_2.src.jar -- Contains the source code for the current release. The javadoc stuff for the software can easily be generated (assuming you have "make") by unjaring the file, going to the directory Java-DODS and doing a "make doc". If there is a problem with the javadoc generation, make sure that the Java-DODS directory is named on your CLASSPATH environment variable. If you don't have "make" then get your CLASSPATH straight and then look at the build target "doc" in the file Java-DODS/Makefile (not that the "\" character is a line continuation flag) and run the javadoc command you find there. If that doesn't work, maybe you should just download the documentation bundle. The example client, "" is located in the directory Java-DODS/dods/clients/geturl. I didn't write this client and it does not currently have much in the way of javadoc info. The best thing would be to read through it's source code. If you are using binaries that you have compiled in this source code tree then the directory Java-DODS directory should be on your CLASSPATH (for example on my system the directory "/home/carbon/ndp/Java-DODS" is on my CLASSPATH) ---- dods.v_1_0_2.Combined.jar -- This file contains BOTH the source code tree and the binary distribution file. Unjar it, you should get the same directory tree that you get when you unjar the "dods.v_1_0.Src.jar" file with the addition of the dierectory "Java-DODS/lib" wherein you can find that crucial file "dods.jar" ---- I realize that the organization of this combined dis- tribution may seem a bit capricious. Allow me to explain my thinking: By including the "jar ball" of the binary distribution in the lib directory you can include it on you CLASSPATH and never actually have to look inside. IF you want, you can compile the source, but if your compilation effort is for some reason unsuccessful (for example you don't have javacc) then it's no big deal. If I had left the .class files distributed around the source code tree then partial compiles or errant "make clean" commands could wipe the binary out inadvertently. I am sure there are draw backs to this, and if you see obvious ones let me know. I am still working out best practices here... In addition I have a site which contains information about the design of the DODS java software. Check out: I think between that and the descriptions of the DODS datatypes found at the DODS home page: You could get started. Write if you get confused. Enjoy! Nathan -------------------------------------------------------------------- Nathan Potter Senior Software Engineer Distributed Oceanographic Data System College of Oceanic and Atmospheric Sciences Oregon State University 104 Ocean Admin. Bldg. Corvallis, OR 97331-5503 email: voice: (541) 737-2293 fax: (541) 737-2064 -------------------------------------------------------------------- -------------------------------------------------------------------- 10/13/00 Placed the majority of the server diagnostic output under conditional control. Found and fixed several bugs in the server code including: * Problem with the string types where if a user requests variable x from a server and constrains it on y and y is a string the server was returning y too. (example: http://DODS.URL/dataset.dods?x&y="bob") * Constraint Expressions were simply not working. * The right operand in the Clause's of the constraint expression was not being correctly marked by the ExprParser (thnaks to James G. for the fix.) This should help things a bit. -------------------------------------------------------------------- -------------------------------------------------------------------- 06/11/01 Repaired DODS relational Database Server (DRDS, dods.servers.sql.drds) so that it correctly handles "null" values in the backend database tables. Repaired DODS Test Server (DTS, dods.servers.test.dts). Test server output is now stable. --------------------------------------------------------------------
Proudly Served by LiteSpeed Web Server at Port 443