DAP2 Protocol Java Software
Greetings,
This is a Java implementation of the OPeNDAP DAP2 Protocol.
In this file you will find:
Also included are:
We hope we hope you find this software useful, and we welcome
your questions and comments.
To contact us, please email technical support: support@opendap.org
Dependencies
Java Virtual Machine
Java 2 Standard Edition (J2SE)
Minimum: Java 1.5
Recommended: Java 1.6.x
This software was developed and tested against the 1.6.0 release of the J2SE
3rd Party Libraries Required by the DAP2 Software
The core software depends on several third part libraries. All of these are
included with the distribution (in the lib directory). These (should) be the ones that the code
was compiled against for development and testing purposes.
- JDOM package, version 1.0, available from jdom.org
- Apache HttpComponents HTTP Client package, version 3.1, available from hc.apache.org
- Apache Commons Codec package, version 1.3, available from commons.apache.org
- Apache Commons Logging package, version 1.1, available from commons.apache.org
- Apache MIME for java package, version 0.6, available from james.apache.org
- Apache Xerces XML Parser package, version 2.9.0, available from xerces.apache.org
It is possibly (in fact likely) that newer versions of these libraries are available from the
various development teams that create these products. Replace them at your
own risk.
Installation
Installation should be quite simple, just make sure that the dap2-server-x.x.x.jar file, along with the
additional library jar files are your CLASSPATH in order for the DAP2 software to work.
Sanity Check In order to verify that you have the software and JVM sorted try the following in a shell(command line):
- Change working directories to the top level of the unpacked distribution.
- Run the following command:
-
java -cp dap2-1.0.0.jar:lib/apache-mime4j-0.6.jar:lib/commons-codec-1.3.jar:lib/commons-httpclient-3.1.jar:lib/commons-logging-1.1.jar:lib/jdom-1.0.jar:lib/xercesImpl-2.9.0.jar:lib/xml-apis-2.9.0.jar opendap.util.geturl.Geturl -d http://test.opendap.org:8080/opendap/data/nc/fnoc1.nc
If you get back a DDS document then everything worked. If you get back an error please look at the text carefully. It may be that the is an issue with the remote server. Or, there may be an issue with the formulation of that command. The error text should help you distinguish the two. (See Note below)
Note: This command was formulated for the dap2-server-1.0.0 release. If for some reason it doesn't work for you it may be possible that this part of the dopcumentation was not updated to reflect name changes or dependancies in the current release. The correct construction of this command to include as parameters to the classpath parameter ("-cp") the dap2 release jar file name followed a colon (":") followed by a colon sperated list of the every jar file name in the lib dir, as modeled above. The next parameter in the command is the full name of the class to run, in this case opendap.util.geturl.Geturl. This is followed by a switch indicating the type of DAP response to get, in the above example it's "-d" which tells Geturl to get the DDS response (there is a "-h" help option too). The final parameter is the data resource URL of a DAP2 dataset available over the internets, in the example above that's:
http://test.opendap.org:8080/opendap/data/nc/fnoc1.nc