|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 14
Messages: 14
Messages: 14
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Java 6 JSRs Pass
Java 6's component JSRs have passed, along with the Java 6 umbrella JSR, which solidifies the official release components and clears the way for Java 6 to be finalized and released. Important JSRs here include JDBC 4.0, the Compiler API, the scripting interface, and the common annotations.
It's a good time to consider Java 6's future. With a new license potentially on its way, and Java 6's feature set getting finalized (along with working implementations of the feature set), Java 6 might be mature enough and open enough to have a broad impact on the industry. However, one has to consider the current installed base of older versions of Java, many of which are effectively immovable (still using 1.3 or older, or 'updated' to 1.4, for example.)
What are your opinions of the Java 6 release? If you're planning on using it, what's your deployment environment? Do you see production environments updating any time soon? Why or why not?
|
|
|
Message #221754
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Java 6 JSRs Pass
Using Java 6 will in most cases depend on support by the application server vendors and 3rd party API's.
I for one would love to use the new features of Java 6 (currently we work with Java 5 in most cases)
A simple reason for me is that Java 6 provides a global performance gain, which is always interesting. There are some new features that i could use but most of the features aren't realy interesting for my line of work.
|
|
|
Message #221760
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
API-partitioning seems to be missing
Unfortunately it seems that the API will grow again and the partioning will not be included.
|
|
|
Message #221769
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: API-partitioning seems to be missing
That's something that i'm also missing. They put a lot of new API 'parts' in there but i'm sometimes questioning why they add it to the base of Java and not as some sort of module.
|
|
|
Message #221791
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
logging enhancement
Give slf4j a try:
http://www.slf4j.org
It's meant as a replacement for commons-logging and is marvelous together with logback (<- meant as a replacement for log4j).
It's made by the guys responsible for log4j and addresses many of it's shortcomings - i.e. parametrized logging strings are only constructed IF they are really logged (rendering .isDebugEnabled() obsolete :D).
Check it out, I'm pretty happy with it ;)
|
|
|
Message #221810
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: API-partitioning seems to be missing
Unfortunately it seems that the API will grow again and the partioning will not be included.
An honest question - what problem would partitioning of the JRE solve?
The Java 6 beta JRE is 15MB for Windows. That is no more than a few minutes download on my broadband connection.
Look at the alternatives - JRE split into a series of modules, any of which may have to be download by an end user separately from the JRE core in order to run a specific Java application. The modules may have mutual dependencies and version control will be important.
What matters is not size of API, but convenience of distributing or downloading and installing the JRE. At 15MB, I really don't think this is a problem, especially considering the alternative.
|
|
|
Message #221835
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: API-partitioning seems to be missing
An honest question - what problem would partitioning of the JRE solve?
Well there are some things that should never be part of the JSDK ... Derby for example, but in general I agree that modularity isnt *currently* an issue. Splitting the libraries from the JVM would be worthwhile. Also having real deprecation of outdated or just plain badly implemented methods/classes. The current luddite "we'll mark that as deprecated even though we havent got the guts to remove it" attitude is a joke. Having the courage to even remove things deprecated in JDK 1.3 or earlier (which will soon be no longer supported anyway) has to be the first step.
|
|
|
Message #221837
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: API-partitioning seems to be missing
An honest question - what problem would partitioning of the JRE solve?
Well there are some things that should never be part of the JSDK ... Derby for example, but in general I agree that modularity isnt *currently* an issue. Splitting the libraries from the JVM would be worthwhile. Also having real deprecation of outdated or just plain badly implemented methods/classes. The current luddite "we'll mark that as deprecated even though we havent got the guts to remove it" attitude is a joke. Having the courage to even remove things deprecated in JDK 1.3 or earlier (which will soon be no longer supported anyway) has to be the first step.
I still don't see what actual problems this is supposed to solve. Why split off libraries? What is the point of removing deprecated methods? Having them still there is not a joke for anyone still running old binaries - people are still running code compiled for Java 1.3. There is no point about taking a courageous step if there are no current issues that taking that step will deal with.
Also, why should the content of the JDK be any problem? Surely size is only really important for the JRE.
So, again, my question is... what are the current problems with the JDK/JRE that require such actions?
|
|
|
Message #221855
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: API-partitioning seems to be missing
I still don't see what actual problems this is supposed to solve. What is the point of removing deprecated methods?
You might think that looking at the javadocs for java.util.Date is all lovely when you see 90% of the methods deprecated but the vast majority dont. It's seen as "clutter" and unnecessary baggage. It's additionally the cause for additional testing overhead ... presumably the JDKs run unit tests. So JDK providers have to maintain methods that were seen as needless 8 years ago. Removal removes clutter. It focuses attention on the methods that people are *supposed* to be using. If a class was immediately (next JDK release) seen as not a good idea then it is currently left in, and has to be maintained, and open to use and abuse.
Removal of deprecated methods/classes doesnt mean i'd be in favour of removal of what some see as "minority interest" parts of the JDK (retaining some magical 20% most used ... which is impossible to define anyway). Having a large API is a good thing and provides the power of the language.
Hacking off cruft (removing deprecated classes/methods) does nothing to weaken the language, and in fact strengthens it because people can be more focussed on the best way of using it.
|
|
|
Message #221870
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: API-partitioning seems to be missing
I still don't see what actual problems this is supposed to solve. What is the point of removing deprecated methods?
You might think that looking at the javadocs for java.util.Date is all lovely when you see 90% of the methods deprecated but the vast majority dont. It's seen as "clutter" and unnecessary baggage. It's additionally the cause for additional testing overhead ... presumably the JDKs run unit tests. So JDK providers have to maintain methods that were seen as needless 8 years ago. Removal removes clutter. It focuses attention on the methods that people are *supposed* to be using. If a class was immediately (next JDK release) seen as not a good idea then it is currently left in, and has to be maintained, and open to use and abuse.
Removal of deprecated methods/classes doesnt mean i'd be in favour of removal of what some see as "minority interest" parts of the JDK (retaining some magical 20% most used ... which is impossible to define anyway). Having a large API is a good thing and provides the power of the language.
Hacking off cruft (removing deprecated classes/methods) does nothing to weaken the language, and in fact strengthens it because people can be more focussed on the best way of using it.
Perhaps, but I still don't see this as anything of great importance to the user of the JDK or JRE. I mean, if you want to be focussed on the best way, just don't use deprecated methods! My feeling about this is very much to leave things alone; Java has an outstanding reputation for backwards compatibility - it would be a shame to break it just for this....
|
|
|
Message #328620
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Nice Post
Firstly, that this isn't just Apache vs Sun. Other members of the Executive Committee have been willing to side with Apache and vote against Sun (February and December 2007). Bear in mind that those members have access to even more information than is public here in order to judge which way to vote. Remember though that those votes are not-binding. Due to the structure of the JCP, the other Executive Committee members cannot actually intercede on behalf of Apache.
London Escort Agencies | Escorts London
|
|
|
Message #329140
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Nice Post
Thanks for sharinng the comparison.I got the news that there is a merger going on between the two big giants. Thanks
cheap web hosting | MCPD
Firstly, that this isn't just Apache vs Sun. Other members of the Executive Committee have been willing to side with Apache and vote against Sun (February and December 2007). Bear in mind that those members have access to even more information than is public here in order to judge which way to vote. Remember though that those votes are not-binding. Due to the structure of the JCP, the other Executive Committee members cannot actually intercede on behalf of Apache.
London Escort Agencies | Escorts London
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
