Yesterday, one of the JAXB users sent me an e-mail, asking for how to solve the problem he faced.
The scenario was like this; you have a client and a server, and you want a client to send an XML document to a server (through a good ol' TCP socket), then a server sends back an XML document. A very simple use case that should just work.
The problem he had is that unless the client sends the "EOS" (end of stream) signal to the server, the server keeps blocked. When he modified his code to send EOS by partial-closing the TCP socket (Socket.shutdownOutput), the server somehow won't be able to send back the response saying the socket is closed.
The Java User Groups Community aims to be the meeting point for JUGs, in order to create a better interaction among the groups, expanding and strengthening the Java movement worldwide.
Here, in the JUGs Community page, JUG leaders and JUG members can come to share information about creating, joining and running a JUG, and to work together in tools, projects and discussions that are important for the worldwide Java community.
As a community of JUGs, projects submitted to this community must represent groups of users, that focus primarily in Java and Java-related technologies. Each JUG project can have their own technical sub-projects.