classpath-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cp-patches] The version numbers


From: Meskauskas Audrius
Subject: [cp-patches] The version numbers
Date: Wed, 29 Jun 2005 14:06:11 +0200
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Roman Kennke wrote

You often mention version numbers like 1.2 and 1.3. This question may be naive, but do they refer to JDK version numbers or to CORBA spec version numbers?

When speaking about implemented/missing CORBA features, I always use JDK version numbers. If I need to refer some other kind of version like CORBA (we write CORBA 3.0.3) or GIOP, I usually state this in the same sentence, as these numbers are not related to JDK versions. Since JDK 1.3 Sun introduces the new group of interfaces, names ending by *Operations (for instance NamingContextOperations) and moves there methods that were previously defined in the main interfaces (like NamingContext). The main interface still contains the definitions of these methods as it inherits them from its *Operations interface. This have nothing to do with CORBA or GIOP version, being a feature of the java API.

In the current Classpath state, the SAME methods are defined TWICE: first in the NamingContextOperations interface that appears since JDK 1.3 and then in the older NamingContext interface, present since JDK 1.2. Since JDK 1.3 the NamingContext inherits the method definitions from NamingContextOperations. Same about BindingIterator and BindingIteratorOperations.

The reason of doing this is that I was not sure which version is our primary target and did not want to remove JDK 1.2 methods just because they are absent since 1.3 and later.

Cheers
Audrius






reply via email to

[Prev in Thread] Current Thread [Next in Thread]