Abstract: A session is established between a user system and an existing version of a network application. Once the session is established, session information corresponding to the session is determined and then communicated to the user system. The session information typically includes a version identifier that identifies the existing version of the network application. Requests received during the same session are accompanied with the session information. The session information is used to route the requests to the existing version of the network application.

Abstract: Under the present invention, a session is established between a user system and an existing version of a network application. Once the session is established, session information corresponding to the session is determined and then communicated to the user system. The session information typically includes a version identifier that identifies the existing version of the network application. Requests received during the same session are accompanied with the session information. The session information is used to route the requests to the existing version of the network application.

Abstract: A session is established between a user system and an existing version of a network application. Once the session is established, session information corresponding to the session is determined and then communicated to the user system. The session information typically includes a version identifier that identifies the existing version of the network application. Requests received during the same session are accompanied with the session information. The session information is used to route the requests to the existing version of the network application.

Abstract: A method is presented for managing applications using application-based names. A naming service registers an alias name; the alias name represents a first compound name that includes an application name that is associated with an application and a deployment name that is associated with a deployment attribute that characterizes a deployment of an instance of the application. The naming service is also able to generate an application-based name associated with an application; the application-based name represents a context within a naming system, and the application-based name is a second compound name that includes the alias name. Applications are managed within a data processing system using application-based names. The first compound name can be associated with a first topology-based name that represents a first context for organizing files that are related to the instance of the application.

Abstract: An adapter is generated by introspecting on the interfaces of an Enterprise JavaBean (EJB) running on a CORBA server. The adapter resides on the Java client-side and contains a remote proxy of the CORBA server that runs the EJB. The adapter is a Java class that implements the interfaces specified by the EJB for invoking its business methods. Adapters delegate all of the business method calls from the client to the CORBA proxy on the server and perform data marshalling from the Java client to the CORBA proxy and vice versa. Any business method calls made by the client to the adapter are delegated by the adapter to the CORBA proxy after appropriate data conversion. Thus, the adapter acts as transparent glue between the Java client and the EJB on the CORBA server.

Abstract: Under the present invention, a session is established between a user system and an existing version of a network application. Once the session is established, session information corresponding to the session is determined and then communicated to the user system. The session information typically includes a version identifier that identifies the existing version of the network application. Requests received during the same session are accompanied with the session information. The session information is used to route the requests to the existing version of the network application.

Abstract: An adapter is generated by introspecting on the interfaces of an Enterprise JavaBean (EJB) running on a CORBA server. The adapter resides on the Java client-side and contains a remote proxy of the CORBA server that runs the EJB. The adapter is a Java class that implements the interfaces specified by the EJB for invoking its business methods. Adapters delegate all of the business method calls from the client to the CORBA proxy on the server and perform data marshalling from the Java client to the CORBA proxy and vice versa. Any business method calls made by the client to the adapter are delegated by the adapter to the CORBA proxy after appropriate data conversion. Thus, the adapter acts as transparent glue between the Java client and the EJB on the CORBA server. The method may be generalized for a client object and a server object implemented in different languages. An adapter may wrap an object reference for a server object.

Abstract: In scripting connections between objects within a component software architecture, a generic event processing module is provided to listen to all possible events. Objects registered for scripting are introspected to determine all events which may be fired by the object. In the case of the Java beans specification, this includes both Java-defined and user-defined events. One or more event listener classes for user-defined events may then be created, instantiated and added to the registered objects at runtime. When an event is fired and detected by a system listener, the appropriate event listener notifies the client, which may be a scripting component. The client may then take appropriate action. With an event processing module as described, event sinks need not be wrapped to become event listeners and event sources need not be wrapped to generate events in a specific manner. Events may be passed between sources and sinks without either knowing of the existence of the other.

Abstract: A method for persisting a container-managed server object or bean in a distributed data processing system is provided. A method in a Tie object is invoked by the container of the bean to assist in the persistence of the bean. The bean may have container-managed fields of both primitive and complex data-types, and the complex data-types may include references to other objects or beans. The Tie object obtains the object reference to the other object. The Tie object unwraps an adapter from the object reference to obtain a proxy of the referred object and stringifies the proxy. The string is then stored by the container in a back-end data store as a known primitive data-type. The referred object may be resurrected by unstringifying the string and reversing the process.

Abstract: A scripting environment component provides predefined interfaces for scripting registered objects. A scripting component implemented for a user-selected scripting language, which implements all methods and interfaces specific to the selected scripting language, connects a scripting engine for the selected language to the scripting environment and the objects registered with the scripting environment. Scripting components for specific scripting languages are subclassed from a generic scripting component. To create and edit scripts connecting objects registered with the scripting environment, the appropriate scripting component is selected to provide connections between the scripting engine for the selected scripting language and the interfaces defined by the scripting environment. Runtime-only information for generated scripts may be saved to a separate storage space. At runtime, the scripts may call other scripts, possibly written in a different language, and respond to events fired by a registered object.

Abstract: For scripting objects in a component software architecture, a generic IDE interface to scripting IDEs is defined to allow connection to a language-specific scripting IDE preferred by a user. IDE class information--methods, properties, and events, including callback methods--for IDE editable objects are saved with an IDE instance of the IDE editable objects corresponding to objects registered for scripting. The IDE instance and its handle are connected to a scripting component through a corresponding Java object and handle. Language-specific scripting IDEs may thus be connected to a scripting component for a different language-specific scripting engine. Any scripting IDE may therefore be utilized for creation and execution of scripts written in a specific language for any scripting engine, allowing the user to employ a preferred scripting IDE regardless of the scripting language selected to connect registered objects.