org.astrogrid.*.
[Update: code developed from iteration 3, when Maven was adopted, is in astrogrid.*, not in org.astrogrid.*
-- GuyRixon - 11 Sep 2003]
Code written by Astrogrid for applications that will run on the Grid should be complete in a subpackage of org.astrogrid. For example, the ACE service (SExtractor wrapper) is in org.astrogrid.ace and subpackages. Client tools should be in a separate peer package, in the case of ACE this is org.astrogrid.aceclient.
General code written by Astrogrid team members but are for more general use, such as xml tools or general UI components, are currently in no general package space. This is probably Not Good and should be sorted out...
See http://forum.astrogrid.org/read.php?TID=251 for the discussion on this so far.
MySpaceGridClient, and at some point presumably for providing 'real' Grid services.
Two implementations of vanilla FTP have also been introduced temporarily, via MySpaceGlobusFtpClient and MySpaceEdtFtpClient. These can generally be deleted in your local workspace; there is also a MySpaceSunFtpClient which uses the unsupported built-in FTP client supplied by Sun. If you do want to use the others, get the librarires from vanilla FTP from Globus and EnterpriseDT Client FTP
> AladinAceClient. Delete the class/exclude from your build if you like.
Axis. Include axis.jar, commons-discovery.jar, commons-logging.jar
log4j - comes with axis anyway I think
Xerces parser - needed as it validates, unlike the sun standard one.
Ideally you want Sun's XML Web Services Developer Pack for the generalised SOAP handling (rather than Axis specific). I had trouble installing this on Linux, in which case the Summer release XML pack will do.
![]() |
Click here for the AstroGrid Service Web |
This is the AstroGrid Development Wiki |
|