With JSR-310 recently accepted as a new JSR, I think it is safe to predict that this will form a significant component of what will eventually become Java 7. While it may not be the most exciting new standard -- at least in terms of bleeding edge technologies, it's impact will be felt heavily across many established a APIs.
Personally, I would have loved have this effort run concurrently during my tenure as JDBC Specification Lead, particularly in the early stages of JDBC 4.0. The frequent mis-understandings in design, intent and general functionality of the JDBC java.sql.Date, Time and Timestamp always stood out high as some of the interfaces were long over due attention, especially considering the strained relationship between java.util.Date and java.sql.Date. Not to mention some of the inherent performance inefficiencies, that are rooted in the java.util.Date class, the general malaise was tolerated for too long.
My current wish list for this JSR runs as follows...
Finger-pointing aside, I must give credit to the co-specification leads, Stephen Colebourne and Michael Nascimento who I believe have an unenviable task. In the new spirit of Java openness they have also added a wiki where you voice your opinions directly. For some well informed opinions, I recommend checking out the Javaposse.com for some well thought out opinions on this topic.
While undoubtedly they will be swamped with comments, we should all set out with the knowledge that it will be next to impossible to keep everyone happy. Nonetheless, I am willing to bet that this JSR will quickly reach the shrill levels of the JDO/EJB/Persistence debate at least in the next couple of months...
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.