Tatjana Baranova authored Nov 26, 2010 and Tigran Mkrtchyan committed Nov 26, 2010

client should has to sequences to track:
  open state id
  created sessions

Make both as dedicated methods in NFSv4Client class.
Move state/session verifications into correspondiong
methods.

Signed-off-by: Tatjana Baranova
Signed-off-by: Tigran Mkrtchyan

updated: guava, logback, slf4j, spring

Tatjana Baranova authored Nov 10, 2010 and Tigran Mkrtchyan committed Nov 10, 2010

Signed-off-by: Tatjana Baranova
Signed-off-by: Tigran Mkrtchyan

maven3 cleanup

maven3 cleanup

Going into direction of IPv6. Uses Google Core Libraries for Java 1.5+

Tatjana Baranova authored Oct 27, 2010 and Tigran Mkrtchyan committed Oct 27, 2010

Each NFSv4.1 server needs it's own session tracking. This
becomes more important when two and more servers in
a single JVM.

Signed-off-by: Tatjana Baranova
Signed-off-by: Tigran Mkrtchyan

Tatjana Baranova authored Oct 27, 2010 and Tigran Mkrtchyan committed Oct 27, 2010

Signed-off-by: Tatjana Baranova
Signed-off-by: Tigran Mkrtchyan

Thread should be named in order to make it
easier to debug the application.

Acked-By: Paul Millar AT desy de

earlier drafts of 4.1 spec ( or by internal developer convention)
the sequence calls was not tracking sessions.

add Tatjana as a developer

enable glassfish maven repository

while java do not have unsigned types files MAXINT become negative values.

Acked-By: Gerd Behrmann