Closing sockets issue

[Betta78]

It seems that there is bug in closing sockets.
The server using this module lists many CLOSE_WAIT related to BaseX Connection

[cmarchand]

The bug is pretty complex to solve :
I have to keep the connection open until all results (the item of the returned sequence) are fetched.
If you fetch all results, I can detect that sequence is at its end, and close the connection ; but if you do not use the result (you do not fetch until end), I can not detect you do not want anymore results, and have to keep the connection open.
But, the connection has a 5s timeout, so is closed after 5s of inactivity ; so it should be automatically closed.

I have changed the code to close the connection when the end of sequence is reached ; please have a test and let me know if it's OK for you. Well, it's not yet build...

[cmarchand]

Release 1.1.0-RC2 published.
Add this to your pom.xml :

<dependency>
    <groupId>top.marchand.xml.ext-funct</groupId>
    <artifactId>basex</artifactId>
    <version>1.1.0-RC2</version>
</dependency>

There is still a log in default console when connection is closed. Will be removed in final release.