 |
Search |
 |
|
|
Yesterday Never TomorrowsPosted by editor on September 18, 2008 at 7:28 AM PDT
Will JSR 310 finally bring sense to Java dates and times? Time-keeping is one of those problem domains that's nice and easy until it isn't. I think I got my first taste of this when I was working the overnight shift at CNN during a change from daylight savings time to standard time. Because you set your clocks back at 2AM, we had two 2AM shows that night: one for 2AM Eastern Daylight Time, followed immediately by one for 2AM Eastern Standard Time. This also made scheduling nice and tricky for all involved, and everyone on the overnight shift picked up an hour of overtime, because we had to work 9 hours instead of 8 to get from 11PM to 7AM the next day. Would your scheduling application have handled the change correctly? Or would you have just added 8 hours to 11PM and thereby miss the extra "fall back" hour? Date and time management in Java has been a mixed bag from the beginning. The handling of absolute times is simple enough: since Java 1.0, Maybe the third time will be the charm. In our Feature Article, Jesse Farnham takes a look at JSR 310: A New Java Date/Time API.
This is another JSR that's on track for inclusion for Java 7, so jump in if you want an advanced look at what you'll hopefully be using this time next year. In Java Today, the SDN continues a tutorial in its Core Java Technologies Tech Tips series with Exchanging Data With XML and JAXB, Part 2. "In this tip, you'll learn how JAXB's binding customization features can facilitate XML processing for the recipient of data as well as for the sender. Binding customization offers a level of control over the characteristics of the Java classes generated by the JAXB schema compiler. This allows you to work with an object model that makes sense for your business domain even when processing XML instance documents based on a schema that is not of your own design." Making use of MarkMail's tools for searching java.net mailing lists, The Aquarium notes Growth in OpenESB mail traffic and wonders if it might be a leading indicator of interest in the project. "The OpenESB mailing lists are showing a significant growth in traffic this month. It is just the 17th and the Combined Traffic so far is 1384 (up from 765 for all of August), while the USERS Traffic is 419 (up from 190 for all of August)." No one writing Java applications should be without an understanding of how to fix things when they go wrong. Diagnosing performance problems can be difficult; sometimes even knowing where to start is hard. In a podcast from TheServerSide, Java Performance Tooling, Dr. Holly Cummins will introduce a number of tools for identifying and fixing common Java performance problems. Today's Weblogs begins with John Vieten showing off a technique for Full-duplex communication with the Grizzly Framework. "I recently joined the Grizzly Project as a committer. One of the first things I did is write a Tutorial on How-to write a custom protocol with the help of Grizzly. [...] So I thought it should be very easy to come up with a Grizzly Demo version of Rex Young's Port Implementation. And here it is." Felipe Gaucho brings up a security concern in Compiling your own byte array Trojan with JAXB 2.0. "Do you mind about the quality of the code generated by automatic tools? I do care, specially when a warning of Findbugs makes sense against code generated by JAXB 2.0." Finally, Cay Horstmann reports that he's been Teaching Software Engineering with BlackBerry. "One of the best aspects of my job as computer science professor is that I keep learning new stuff. This semester, I am teaching a software engineering class. Cinequest, the organization that puts on the annual San Jose film festival, approached the CS department, asking for help with their mobile initiative. We jumped at the chance, and now my students are hard at work designing and prototyping a BlackBerry application for festival attendees."
In today's Forums,
Finally, Clive Brettingham-Moore explains WSDL port management in Re: How to override endpoint address of service from client code. "You don't need to dynamically add ports if you have specified WSDL, either using Service.create(URL,QName) or a generated Service class (instances of gererated service are just like the two arg create; the default constructor simply uses a default WSDL URL & QName). As you have noticed Service.create(QName) is really only useful for Dispatch, but the two argument method (and subclasses) will work out the ports from the WSDL (WSDL is also needed for the getPort methods to work)." Current and upcoming Java Events :
Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site. Archives and Subscriptions: This blog is delivered weekdays as the Java 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 java.net Archive. Will JSR 310 finally bring sense to Java dates and times? »
Comments
Comments are listed in date ascending order (oldest first)
Submitted by mrmorris on Thu, 2008-09-18 16:40.
And here I though you had some insight into a new 007 title. :p
|
|
|
||
|
