-Provides access to the components and profiles in an IOR without the overhead -of CDR encoding. -
-The abstract model of IORs works as follows: - -
-In all cases, containment is represented by having the appropriate interface (IOR and -IIOPProfileTemplate above) extend java.util.List. This makes it easy to use all of the -facilities in the Java collections framework with IORs. However, note that all -objects available through these APIs are immutable. Thus all list update operations -through UnsupportedOperationException, and list iterators cannot modify the underlying -list. -
-Templates are used because the basic object adapter model for object creation is to -establish all properties of an IOR (except for type and object ID) when the object -adapter is created. This has been present for the POA essentially from the beginning, -since policies can only be passed to create_POA, and cannot be changed on an existing -POA. The Portable Interceptors work has also made this clear, since the IOR interceptor -runs only when an object adapter is created, which is the only time that user code -can add tagged components to an IOR. - - -