Re: Java 8 Lambda binary snapshot

On 11/16/2011 1:28 AM, Lew wrote:
Arne Vajhøj wrote:
Lew wrote:
Why don't the vendors certify for the later Java in anything less than five years?

It's the same question. Pushing it back one level doesn't answer it.

Usually app server versions and specific JVM versions are tied.

It is even in the specs.

Java EE 6 spec:

This specification requires that containers provide a Java Compatible™
runtime environment, as defined by the Java Platform, Standard Edition,
v6 specification (Java SE).
...

And?

That says nothing about the vendors or why they lag the specs for so
long. It is a summary of the specs that they might lag.

The vendors release new versions of the app server that works
with new EE or SE versions.

But they don't certify a given app server version for new SE versions.

And the specs support that policy.

Arne

.

Relevant Pages

  • Re: Java 8 Lambda binary snapshot
    ... This specification requires that containers provide a Java Compatible™ ... That says nothing about the vendors or why they lag the specs for so long. ... and, people who want scripting languages mostly want lots of features and for everything to be doable with a minimum of effort, but largely forsake both performance and reliability in doing so. ... sadly, my scripting language/VM has also been somewhat tending towards internal complexity as well. ...
    (comp.lang.java.programmer)
  • Re: java performance w2k vs NT4
    ... My first thought is that similar specs may be different enough. ... Sun Certified Java Programmer for J2SE ... > server based (but not Java connection, ... but CPU usage seems to be more intensive on the w2k ...
    (comp.lang.java.developer)
  • Re: Java 8 Lambda binary snapshot
    ... Usually app server versions and specific JVM versions are tied. ... This specification requires that containers provide a Java Compatible™ ... That says nothing about the vendors or why they lag the specs for so long. ...
    (comp.lang.java.programmer)
  • Re: InetAddress.equals() Anomoly?
    ... >> 1) The J# implementation is buggy because it does not follow the specs. ... > the very earliest of development of the Java language to be able to handle ... which converts DNS names to conical DNS names if the DNS server ... > InetAddress is exactly what its name implies: ...
    (microsoft.public.dotnet.vjsharp)
  • Re: InetAddress.equals() Anomoly?
    ... > 1) The J# implementation is buggy because it does not follow the specs. ... The Java spec for object equality was written in the very ... converts DNS names to conical DNS names if the DNS server returns that, ... InetAddress is exactly what ...
    (microsoft.public.dotnet.vjsharp)