Popular @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
NetBeans 6: Matisse Updates
NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
Introduction to Groovy Part 3
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Easier Custom Components with Swing Fuse
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Benchmark Analysis: Guice vs Spring
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Java EE 6 Spec Finalized and Approved
URL: internetnews.com
At 3:35 AM on Jul 19, 2007, Michael Urban wrote:
Fresh Jobs for Developers Post a job opportunity
Among those that voted for approving Java EE 6 were IBM, Red Hat, and Google. The Apache Software Foundation was the only member of the executive committee that voted against the spec. Apache's no vote was not with regard to a problem with the spec, but rather, was a vote against Sun's leadership of the spec.
According to the vote log, Apache had this to say:
"The Apache Software Foundation's vote is based on the point of view that this spec lead -- Sun -- is in violation of the JSPA [Java Specification Participation Agreement] and therefore shouldn't be allowed to start another JSR [Java Specification Request] until the above matter is resolved. This vote is not a comment on the technical merits of the JSR. If not for the issue of the spec lead, the ASF would have otherwise voted yes."
Even though IBM voted in favor of the Java EE 6 spec, they also took issue with Sun's licensing:
"IBM's vote is based on the technical merits of this JSR and is not a vote on the licensing terms. IBM supports licensing models that create an open and level playing field by allowing third parties to create independent implementations of Java Specifications and that do not allow individuals or companies to exercise unnecessary control for proprietary advantage."
This is the second time that Java EE 6 has gone before the JCP committee for approval. The first time, it was withdrawn.
Other than the licensing and and leadership issues, most seem to be happy with the technical specifications of Java EE 6. Even Rod Johnson of the Spring project, who has in the past, complained that Java EE was too complex, came out in support of Java EE 6, remarking that "Java EE 6 gets it right".
Original article
12 replies so far (
Post your own)
Re: Java EE 6 Spec Finalized and Approved
There's an interesting sub-thread on Apache's JCP-OPEN mailing list regarding the merits of this latest tactic from the ASF:http://permalink.gmane.org/gmane.comp.apache.jcp-open/700
http://www.jfree.org
Re: Java EE 6 Spec Finalized and Approved
If someone is interested in reading the Java EE 6 specification here is the link:http://jcp.org/en/jsr/detail?id=316
Re: Java EE 6 Spec Finalized and Approved
When are we likely to have a functional implementation of this spec ? I would assume that it has to be/will be implemented by the various application servers out there? So, when would e.g. Glassfish support this ?Re: Java EE 6 Spec Finalized and Approved
IBM include that comment in every JSR they vote on. No big deal.Apache's response is interesting though. I dont think its fair that they'd want to prevent progress with the EE6 JSR just because of an issue they have with the SE JSR TCK, which has nothing to do with EE6, and the spec lead has said that the TCK "field of use" restrictions will NOT be an issue with EE6.
And the title is very misleading. The EE6 specification has NOT been finalised and approved. Not even close. Only the SUBMISSION was approved, which specifies the scope and the goals. The next step will be to form the expert group and begin the real work of hammering out a spec. So there is no EE6 specification yet, though the first drafts should appear in a few months.
Re: Java EE 6 Spec Finalized and Approved
Apache is effectively owned by IBM, a no vote by them is essentially a no vote by IBM that IBM is unwilling to make themselves for political reasons.Expect more of the same as the battle to wrench control over Java away from Sun continues to heat up.
Re: Java EE 6 Spec Finalized and Approved
> Apache is effectively owned by IBM, a no vote by them> is essentially a no vote by IBM that IBM is unwilling
> to make themselves for political reasons.
Do you realize how stupid and insulting this comment is? There are lots of great people at Apache that have nothing to do with IBM.
Why is it when someone or some organization does something contrary to the Sun Java position, the logical conclusion is that they must be fronting IBM? This just seems odd to me?
btw, I work for the Eclipse Foundation, another organization that is often assumed to be a front for IBM. I can assure you we are an independent entity that can think on its own.
Re: Java EE 6 Spec Finalized and Approved
> btw, I work for the Eclipse Foundation, another> organization that is often assumed to be a front for
> IBM. I can assure you we are an independent entity
> that can think on its own.
Does IBM make you say that?
(I'm sorry...I couldn't resist)
Re: Java EE 6 Spec Finalized and Approved
>> Does IBM make you say that? :)
>
> (I'm sorry...I couldn't resist)
:-)
Re: Java EE 6 Spec Finalized and Approved
What *is* the licensing problem exactly? I always had the impression the EE specs were free to implement, pass around,and share?Or is it the requirement of some test-suite-passage that is the problem?
Re: Java EE 6 Spec Finalized and Approved
I guess the problem is that Sun has special powers in the JCP process (i.e. no changes in the JDK without their approval). IBM has a fair part of their family jewels bet on Java. What if Microsoft decides to buy Sun?In contrast, IBM holds no special de iure powers in the Eclipse foundation (de facto is a different cup of tea, who pays the piper...)
Re: Java EE 6 Spec Finalized and Approved
2.13 Please describe the anticipated schedule for the development of this specification.We hope to deliver the final specification, reference implementation, and TCK by the end of 2008. This implies that the specification must reach Proposed Final Draft by early 2008. A rough schedule would be: [schedule]
Source: http://jcp.org/en/jsr/detail?id=316
Re: Java EE 6 Spec Finalized and Approved
Glad to hear the news.The new version always brings new feature,as well as new bug.
Maybe use later is a good idea?
Java Swing