Abstract: A process and system for providing name service scoping behavior is implemented. In an object-oriented data processing system, a request is received for an initial context for a namespace from a requesting object. A scoped initial context factory object is constructed, and an initial context is requested from the scoped initial context factory object. A class for the scoped initial context factory object may be determined from a variable in a hash table object passed as an argument. In response to the request for an initial context from the scoped initial context factory object, an initial context is requested from a non-scoped initial context factory object. The scoped initial context factory object may be a subclass of the non-scoped initial context factory object. The initial context returned by the non-scoped initial context factory object is scoped to a partition of the namespace, and the scoped initial context is returned.

Abstract: A system, method, and program product, in which a stateful EJB session bean is used as the front end to client calls. In this configuration, a queue is represented by a session bean instance. “Put” and “get” are called on the relevant session bean instances. Thus, for example, a client, instead of first finding a home for a given type of OMs then calling “put” on the home to send out messages, will find a session bean home, create a session bean instance corresponding to a queue, and call “put” on the bean instance to send messages. In this manner, the message queue can be managed using standard EJB techniques.

Abstract: The introspection capability of Java is utilized by the described verification tool to verify validity of a target bean's Java Archive (JAR) file. The deployment descriptor class is verified first according to Enterprise Java Bean. specification rules. The remaining classes: remote interface, home interface and bean class are all loaded into a Java Virtual Machine (JVM) and verified by the described verification tool through Java introspection.

Abstract: A process and system for providing name service scoping behavior is implemented. In an object-oriented data processing system, a request is received for an initial context for a namespace from a requesting object. A scoped initial context factory object is constructed, and an initial context is requested from the scoped initial context factory object. A class for the scoped initial context factory object may be determined from a variable in a hash table object passed as an argument. In response to the request for an initial context from the scoped initial context factory object, an initial context is requested from a non-scoped initial context factory object. The scoped initial context factory object may be a subclass of the non-scoped initial context factory object. The initial context returned by the non-scoped initial context factory object is scoped to a partition of the namespace, and the scoped initial context is returned.

Abstract: A technique for providing support for multiple calling conventions for methods and procedures that return structures is provided. A source code of a client program may be compiled by either of two compilers, wherein one compiler employs a calling convention that is different from the first one. A binary library containing a procedure and a converter for each procedure returning a structure to a client program, is provided to support two calling conventions. If the client program is compiled by a compiler using a first calling convention, the program is compiled such that it calls the procedure directly and receives a result, a structure, via the first calling convention. Compiling the client program with a compiler using the second conventions results in calls to the procedure being routed to the converter, which calls the associated procedure, using the first calling convention.