Christian Taylor

Doesn't the container already handle all of this for you? If a page that requires a login is accessed, the request will be intercepted and redirected to the login page, and then redirected back to the original URL after logging in. This assumes that the standard and well-tested container-based security is being used, and you aren't trying to create your own login system for some reason.

I don't feel that splitting a string or parsing JSON should really take much time on modern hardware and browsers, unless it's a serious ton of data but even then it's more likely what you're doing with the data afterwards. Have you profiled your Javascript so you know for sure where it's spending all of its time?

You're welcome, glad it helped

You are binding the server socket to the loopback address:

server.bind(new InetSocketAddress(InetAddress.getLoopbackAddress(), NetConstants.PORT));

So therefore it works on loopback, but not on any other address your system has. If you look at the javadoc for java.net.InetSocketAddress you'll see it has another constructor that takes only a port and binds to the wildcard address, which means any address your system has. Give that a try.

How about StringEscapeUtils from Apache Commons Lang? I've used for HTML and many other things.

I'm not aware that Java 6 corresponds to Tomcat 7 in any sort of way. I've run Tomcat 7 on Java 6, 7 and 8 with no problems.

If you need to produce .class files that run on older versions, have a look at the -target option to javac. You can read about it here: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html

Hope this helps.

J. Kevin Robbins wrote:

Christian Taylor wrote:

J. Kevin Robbins wrote:And incidentally, having multiple tbody elements in one table is invalid html and will only cause you problems.

This appears to be incorrect. According to the specs for both HTML 5 and HTML 4, a table may contain multiple tbody elements.

That's interesting. I stand corrected, but now I'm wondering why you would want to do that.

Grouping of rows could be useful in some scenarios, for styling purposes or possibly manipulating the DOM to sort or move groups of rows more easily than each related row individually. Bear is certainly correct that they don't help anything in this situation and they are being used in an invalid way, so I'll leave it at that and not take this any further off-topic from Yohan's original question.

J. Kevin Robbins wrote:And incidentally, having multiple tbody elements in one table is invalid html and will only cause you problems.

This appears to be incorrect. According to the specs for both HTML 5 and HTML 4, a table may contain multiple tbody elements.