Some people say that you should approach JavaOne like a marathon -- not that I'd know anything about real marathons. Pace yourself, be steady, finish all in one piece.
As a battle-worn JavaOne veteran, I want to agree. I want to believe that the key to a successful experience at JavaOne is to plan ahead and to pace yourself.
I'm always excited when I can get in on the fun those EE guys seem to have all the time.
In another month, you'll be knee deep in AJAX, the Java Persistence API, concurrency, threads, and other great session topics at the 2007 JavaOne Conference.
I know it's Friday, quitting time even, but I have to share one more thing before the weekend.
I've been researching the Java Persistence API (JPA) for an article next month. The persistence API is part of the EJB 3.0 spec. The JPA portion alone is over 250 pages of bone dry annotations, query language, and apis.
The Java SE 6 release provides an interesting new class:
java.net.IDN. It's small, simple...very focused on a single task. That task has two parts:
- to convert domain names from practically any Unicode character to an
ASCII Compatible Encodingor
Storing localized resources for your Java applications usually means creating a
.properties file or a
ResourceBundle subclass. You don't usually have a lot of control over how the resources are cached or how they're stored.
Here's an example. The enforced caching of resources was a common complaint for server applications.
Java SE 6 provides new i18n support in 6 major areas.
The 2007 JavaOne Conference is right around the corner, May 8 - 11. JavaOne is the largest Java technology conference of the year. Drop the excuses, you have to be there.
Regular attendees know that you have to plan things in advance. The number of sessions, the huge crowd, and all the show floor distractions practically require you to plan ahead.
US daylight saving time (DST) changes took effect this weekend. Were you ready? Did you know?
If not, you may still need to read up on the problem.