use GENERATED BY DEFAULT to allow pk insert/update

refs #60
updated javadoc
refactor boolean expressions
skip self-loop edges when orthologizing

refs #53
delete supporting statement when edge is deleted
find kam node id by short form BEL terms
removed jdk6 jdbc api; now compiles with java 7

uses mocks instead of anonymous test classes

upgraded mockito to latest 1.9.5
storing bel statement text in statement table

- column: statement.bel_statement (type: varchar(4000))
- updated all sql scripts
- updated kam import/export table structure
fix for #58; always term/stmt equivalencing

complex, composite, products, reactants, and list term equivalence follow
the commutative property...i.e. order of arguments has no effect on term
equivalence

this fix was addressed previously, but is not being applied because
term and statement equivalencing were not run if a parameter equivalence did
not occur...now all equivalence stages run

closes #58
fixed UNSET ALL / UNSET NAME; #51

UNSET ALL now clears the current statement group annotations if within a
statement group scope otherwise the main scope annotations are cleared.

UNSET NAME can now affect the statement group annotations as well.  Again it
depends on where the UNSET command is issued (statement group / main scope).

fixes #51
fix; quote params in kam node label if necessary

the kam node labels are stored without proper parameter value quoting...this
fix addresses that
enhance; find kam node id by kam node label

improves resolver api to resolve nodes by kam node label
set fixed WSDL for web api; defaults to localhost
just say no...to transforming wsdl locations
deduplicate statements based on evidence
flexible node search for phase III pruning
new Web API call: GetSupportingEvidenceMultiple

retrieves evidence for multiple edges; returns [edge id, statements] object
in order to match with edge input
removed use of java 7 apis for null check

minimal jdk is java 6
fix BEL parser to unquote parameters

unquoting parameters ensure that the parsed AST contains the raw namespace
value stated in the BEL statement
fix pattern to consider valid '_' in value

by definition a value (OBJECT_IDENT in the BELScript grammar) can be a
letter, digit, or an underscore...[a-zA-Z_0-9], so we only need to quote if
we can find a character outside of these ranges, hence find [\W]