Client data in grid viewer

I managed to get AMDS client data in grid viewer after importing several libraries and manufacturing a local temporary client of my own. I am feeling much better now.

The next steps are to get that data on a map... and to get the client out of the "localtempclient" into a cool multi-client that adaptively uses different connection methods depending on the URL provided.

Also, I anticipate a lot of mavening and a lot of jar hunting over the next couple of days.

New repository, building test code, and RODSAdai webapp is lining up

So... Dr. Jeremy Espino helped me get a LOT of stuff done today with RODSAdai.

First off, he had some shell scripts and a repository that is more amenable to deployment... so he just took all the suggested associated jars for ogsadai and put them in that repository... adjusted the pom to point to them, and committed the change.

This basically saved me from having to do a jar hunt, and saved Anurag from having to update our persnickety sourceforge repository.

That being done... I tried to do an mvn package... and it worked this time! So the new jars during packaging are now curing the "but it works fine in the ogsadai directory" problem. I can run secure queries in tests, and have them pass. Thus, I have written some more unit tests and have committed them.

The next thing Jeremy did is build a web project for RODSAdai called RODSAdai-web. I have written (but haven't had a chance to test yet, that will be tomorrow) a little JSP that will essentially call rodsadai, run a method that runs a query, and return the resulting spatial/time series.

Jeremy also set up the dependency to the jar that is built by the RODSAdai project... which includes all the libraries that RODSAdai needs. Hopefully, the inclusion of the jars that made the secure query operate from the junit test framework will also allow the test to operate within tomcat. If it does, then we will basically have a footprint for any jsp-container based ogsa-dai client.

So yeah, tomorrow are the tests... and since we have reached a bunch of milestones in a short time, I am going to start the haltingly-updated, rarely revised "If I get hit by a bus" guide document that should help anyone else who needs to set up RODSAdai do so within a day

Jar hunt finished, maven repository updated, musical servers commencing

So, the jars have been included in the new repository (I had to spend some extra time generating some extra files that is necessary for remote repositories)

Right now, we are dealing with moving a server between VMs, at the end we are hoping to have an ubuntu globus server (the previous server was corrupted by attempts to install dual mysql databases).

Also, for some odd reason, the tests that I was so elated to have working yesterday... are now not working citing an "OGSA-DAI resource null is unknown" error. I am thinking it might be some sort of "the IP has changed" conflict... but at the same time the other OGSA-DAI examples are still working. Either way, I don't think I am going to be able to diagnose it today, and am out of ideas of what to try until we get the other VM set up to match this one.

13 new jars

So... 13 new jars were added to the RODSAdai project in order to get the simple client test working (as opposed to just compiling). 2 of them were extra Ogsadai jars... and the other 11 were based in globus, and it took me all day to ferret them out.

I tried deploying the jars to our repository, but it seems that sourceforge doesn't like something because I kept getting 405 (method not allowed) errors, thus I have sent an email to Anurag to start the process with him since he set up the repository initially...

The other reason I sent him the jars and dependency info is because my main workstation is in the process of being cloned and I wanted to make an email-based backup.

Tomorrow will most likely be spent creating a working Ubuntu globus node, as my current one got corrupted.

Going on a JAR hunt...

Today, I started beefing up the standard JUnit tests in RODSAdai... and remembered that a LOT more code is needed to run OGSA-DAI implementing clients than to just build it.

So, since the new test code runs an OGSA-DAI test... I am having a lot of attempts at "mvn compile", a test error or failure will result, so I check the log, find the class it needs, and make a reference to it, installing it in the maven repository if it was not in the global one, and repeating.

This will probably consume me tomorrow and maybe a bit of friday. I mean it when I say a lot of jars.