Is the Naming Service compatible with the older 3.x Naming Services?
The current 4.x API is to support the latest INS specification and the various new features that are now available. The interfaces available can be divided into the standard and proprietary portions. We still support support the standard 3.x omg NamingContext interface. This hasn’t changed at all. The new INS specification defines a new interface called NamingContextExt that extends from the old NamingContext. All the new methods and extensions are found in this interface. As for the proprietary portion, the NamingContextFactory, ExtendedNamingContextFactory and other new interfaces have moved from the standard org/omg/CosNaming directory to the new com/inprise/vbroker/ExtNaming directory. This is to keep our proprietary extensions and additions in our directory where it rightfully belongs. The above changes may break some of older Naming Service clients. For those clients that stick to the standard OMG interface such as NamingContext, the client doesn’t need any modifications at all.
;;; The current 4.x API is to support the latest INS specification and the various new features that are now available. The interfaces available can be divided into the standard and proprietary portions. We still support support the standard 3.x omg NamingContext interface. This hasn’t changed at all. The new INS specification defines a new interface called NamingContextExt that extends from the old NamingContext. All the new methods and extensions are found in this interface. ;;; As for the proprietary portion, the NamingContextFactory, ExtendedNamingContextFactory and other new interfaces have moved from the standard org/omg/CosNaming directory to the new com/inprise/vbroker/ExtNaming directory. This is to keep our proprietary extensions and additions in our directory where it rightfully belongs. ;;; The above changes may break some of older Naming Service clients. For those clients that stick to the standard OMG interface such as NamingContext, the client doesn’t need any modificati
The current 4.x API is to support the latest INS specification and the various new features that are now available. The interfaces available can be divided into the standard and proprietary portions. We still support the standard 3.x omg NamingContext interface. This hasn’t changed at all. The new INS specification defines a new interface called NamingContextExt that extends from the old NamingContext. All the new methods and extensions are found in this interface. As for the proprietary portion, the NamingContextFactory, ExtendedNamingContextFactory and other new interfaces have moved from the standard org/omg/CosNaming directory to the new com/inprise/vbroker/ExtNaming directory. This is to keep our proprietary extensions and additions in our directory where it rightfully belongs. The above changes may break some of older Naming Service clients. For those clients that stick to the standard OMG interface such as NamingContext, the client doesn’t need any modifications at all. It shoul
