Posted by editor
on January 9, 2007 at 7:10 AM PST
Freezing state for later use... also:
Feature article: Transparent State Management Using the Decorator Pattern
Weblogs: Gosling and "kitchen sink" Java, Properties in Java, and where is Java SE 7 going?
Java Today: NetBeans 2006 in review, Enigma cipher machine in Java3D, and rewriting old games in Java
Forum postings: Heap size for GlassFish, .NET interoperability, and Java SE 7 anti-features?
Freezing state for later use
Achieving state management in web apps, in seeming defiance of the statelessness of HTTP, has long been one of the core challenges of web application development. Without statefulness, your online shopping cart empties everytime you change pages. Not that there aren't answers; there are just a lot of them, some better than others. To the servlet developer, a lot of the solutions involve working intimately with the
HttpSession. But is that necessarily the ideal approach?
In our Feature Article ,
Transparent State Management Using the Decorator Pattern , Sharfudeen Ashraf goes a different direction, putting state management in a servlet filter to a achieve a "transparent" state management system. "If such a mechanism is in place, then web applications can acquire statefulness without having to explicitly deal with state management APIs such as HttpSession. In many scenarios, this would provide a better alternative to the traditional way of explicitly handling session management APIs. The article explains where transparent state management would be useful, and discusses a reusable solution to implement transparent state management. "
James Gosling reports on having some Compiler fun in today's Weblogs . "For years I've wanted to set up a "Kitchen Sink Language " website for experimentation. A place where people could throw language features, no matter how absurd, just so that folks could play around. Now that javac has been open-sourced, it's easy."
FabrizioÂ Giudici comes away from JavaPolis and the recent discussions of closures and properties and wonders
Where are we going? (warning: rants ahead)
"I returned from JavaPolis with a bag of mixed feelings. The good ones: the conference was great, well organized, rich of contents (I'm repeating again, three days of conference for 200€ is excellent price for value), I met people, last but not least the idea of reaching Antwerp by car was very good as I enjoyed my photographic trip through northern France. The bad ones: I'm worried about where Java 7 is possibly going and about the topics that the community is possibly perceiving as the most important."
RichardÂ Bair sounds psyched in
Properties in Java? Hoorah! :
"Properties in Java? Awesome! As with any new language feature, there has been a lot of debate over whether this is an improvement to the language, or a detriment. And of course, every language-designer-wannabe (myself included!) is pounding the pulpit, declaring the One True Way to Property bliss. Well, sit back and enjoy as I pound the pulpit. Because seriously, I really do have the right solution! I promise!"
In Java Today ,
Netbeans.org has posted a year-end summary in NetBeans in 2006: A Year in Review : "2006 was a productive year for NetBeans. It was a year of major releases and debuts. NetBeans traveled around the world and picked up a few new languages. Partnerships were formed; community involvement and outreach expanded. A book was published and a birthday celebrated. And amid all the activity, NetBeans acquired a new image. Join us for a look back at highlights from a year of achievements."
The Java3D Enigma Cipher Machine is a Java-implemented, working 3D model of the historic Enigma cipher machine used by Germany in World War II. The source code for this model serves as a demonstration of how to implement an animated 3D model using Java3D. Additionally, the model may be used in the study of the history of cryptography, giving students an opportunity to simulate the use of a (rare) Enigma machine.
Nigel Hughes blogs on re-implementing an Amiga game in Java in Re-writing history - implementing an old game in Java : "One game we were never able to find a publisher for was called Cascade. It used a really simple algorithm to simulate water a particle at a time, and by manipulating the environment a player would attempt to collect enough water before the time ran out. Well, with a really tightly engineered loop the Amiga version on a 1200 used to manage about 400 drops + the rest of the game engine every 50th of a second. I recently wondered how Java would handle the algorithm and whether a few of the limitations could be worked around. I have to admit, it's looking good! "
In today's Forums ,
djhagberg works through memory settings in
Minimizing (and determining minimum) heap size for GlassFish?
If I leave the default heap size setting -Xmx512m then the Java process for GlassFish ends up using WAY more than 700Mb of RAM, leaving me with nothing left to even run asadmin or a mail server. If I reduce the heap size down to 256m, I get an "OutOfMemoryException: heap..." error about once a day. I'm not /entirely/ sure if this is occurring because of problems in the app, or because GlassFish just needs that much memory. So my question to the folks on this board -- what is the lowest -XmxNNNm size that you have successfully run GlassFish apps on reliably, for more than a week without a bounce?
In Re: Java7 anti-features ,
jwenting expresses concerns about the direction of JDK 7 planning: "Embedding metadata in code is also against everything best practice tells us to do, yet annotations do essentially that. A decade ago it was decided that operator overloading and function pointers were BAD, yet both seem set to make their way into Java. There's screaming for multiple inheritence at class level, another thing that's been recognised as a Bad Thing. Luckily that's not made it (yet), probably because noone has taken the time to write up a nice sounding proposal that will sway the marketing guys who now decide on what the language will be."
has some, but not all, of an interoperability problem figured out in
Java Client <--> WCF Server : How to create and use certificates
I have a WCF Web Service and a Java WSIT client. Using wsHttpBinding I was able to establish a session oriented connection. When I try to encrypt the data flow using message security and certificates it works only with .NET clients. Can anyone give me a detailed description how I can convert a self signed certificate, which I created using makecert and which works fine using .NET clients, into a Java keystore or truststore and how to use these?
Current and upcoming Java
Registered users can submit event listings for the
href="http://www.java.net/events">java.net Events Page using our
href="http://today.java.net/cs/user/create/e">events submission form.
All submissions go through an editorial review before being posted to the
Archives and Subscriptions: This blog is delivered weekdays as
Today RSS feed . Also, once this page is no longer featured as the
front page of java.net it will be
archived along with other past issues in the
Freezing state for later use