[namedgraphs] SWP code refactoring and TriQL removal

[Jennifer C. <jen...@at...>]

Hello All,

As promised, I refactored the SWPNamedGraphSetImpl code as well as
SWPSignatureUtilities, and a bit of SWPWarrantImpl.  These changes, and the
move from TriQL to SPARQL, are included in patch #2496503 on the sourceforge
web site.

(More details on the changes are included in the patch description.)

Tests pass except for the 2 known failures, and it works for my application,
too.

I also used some Java 5 functionality in a few places (so that types are
specified for certain instances of Collections, e.g. (ArrayList<Triple>)).

We can certainly back out of Java 5 requirements if that's important.  I
thought it would be safe to stick that in since we're already using the
bouncycastle library for Java 5 instead of 1.4.

If we do want to move to Java 5 for the project, then (once the above patch,
assuming it is accepted, is applied) I could go through the code and make a
patch that touches many more files and adds more type constraints.  (Or
someone else could, it doesn't matter to me who does it, I just would like
to see it get done.)  I can focus on the non-Semantic Web code and not touch
that or anything else that is actively being updated.

One other thing - I noticed the other day that the web site highlights how
NG4J supports both TriQL and SPARQL.  We'd better update that since TriQL is
already deprecated.  Thanks again to Olaf for making the initial cut at the
removal of TriQL.  That came in handy as I made the modifications!

Jennifer

Jennifer P. Cormier
Sr. Computer Scientist
ATC-NY
www.atc-nycorp.com