February 01, 2011
Mark Wielaard: New GPG key.
Finally created a new GPG key using gnupg. The old one was a DSA/1024 bits one and 8 years old. The new one is a RSA/2048 bits one. I will use the new one in the future to sign any release tarballs I might create. pub 2048R/57816A6A 2011-01-29 Key f...
More »
February 01, 2011
Andrew Hughes: [SECURITY] IcedTea6 1.7.8, 1.8.5, 1.9.5 Released!.
We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.
This update contains the following security updates:
The IcedTea project provides a harness to build the source code from OpenJDK6 u...
More »
December/2024
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 |
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | | | | |
|
|
My top wish for Java 8: EE applications as first class citizens
I have been a Java developer since the 1.02 days. It has been a long and fun ride, and in spite of what people said over the years the Java language and Java platform didn't die and are in fact stronger than ever. But sometimes I wish it would evolve faster.
Java EE has come a long way, to the point Java EE 6 can be considered a lightweight development platform. When Glassfish v3 was released one of the selling points was fast application (re)deployment times. This is an essential feature for any team in the quest for greater developer productivity: if you have to wait 120 seconds for a redeploy and you do it 30 times a day, you spend an entire working hour just waiting for the server to reload your application.
The problem is, even tough Glassfish v3 deploys applications very fast indeed (most of my deployments are under 12 seconds now, for relatively complex web applications) it also suffers from a problem that plagues every single Java EE implementation I have worked with: memory leaks. After very few redeployments the Glassfish JVM dies with java.lang.OutOfMemoryException and you need to forcefully kill it and start another instance. That ends up neutralizing most of the gains obtained with fast deployments.
To be fair, it is not entirely Glassfish fault. I have been spending more time than I would like to admit chasing memory leaks and most of the times the cause lies in some third-pary library used by th...
Date: August, 23 2010
Url: http://www.java.net/blog/jjviana/archive/2010/08/16/my-top-wish-java-8-ee-applications-first-class-citizens
Others News
|