Axis problem has functioning workaround

To address the axis mismatch problem (described here), we developed a separate RODSAdai download servlet that can be called by the RODS application to return either a TimeSeries or SpatialSeries object serialized over HTTP.

Jeremy has tested this in his Pittsburgh environment and it is working.

Mario also mentioned a tool called Jar Jar Links (http://code.google.com/p/jarjar/) that may be able to help. We'll investigate this once the time is found.

So good news is that we're no longer blocking on the custom Axis 1.2RC2 that Globus uses.