Abstract: A method, system and apparatus for performing selective data processing based upon a static analysis of the code of a compiled object. A compiled object, for example an enterprise bean, can be analyzed to determine how individual methods in the enterprise bean access specific objects. Those specific objects can include, for instance, data members of a class, or class objects passed into one or more individual methods of the enterprise bean. Where the individual methods of the enterprise bean do not mutate or otherwise change the state of the specific objects, those objects can be accessed by reference only. Importantly, where the specific objects are data fields linked to a table in a database as managed by a container managed persistence (CMP) bean, an update to the table will not be required when the static analysis of the enterprise bean otherwise indicates that the data fields are merely accessed, but not updated.

Abstract: A method for calling a software method in a called CORBA application by a caller software method in a caller CORBA application in a process of a computer system is disclosed. The caller software method calls a software method in a CORBA stub sending a parameter which is created using a classloader of the caller application. The CORBA stub software method calls a software method in a dynamic proxy sending the parameter. The dynamic proxy software method calls an ORB sending the parameter. The ORB serializes the parameter and returns it to the dynamic proxy software method. The dynamic proxy software method calls the ORB sending the serialized parameter. The ORB deserializes the serialized parameter using a classloader of the called application and returns it to the dynamic proxy software method. The dynamic proxy software method calls the called software method sending the deserialized parameter.

Abstract: A method, system and apparatus for performing selective data processing based upon a static analysis of the code of a compiled object. A compiled object, for example an enterprise bean, can be analyzed to determine how individual methods in the enterprise bean access specific objects. Those specific objects can include, for instance, data members of a class, or class objects passed into one or more individual methods of the enterprise bean. Where the individual methods of the enterprise bean do not mutate or otherwise change the state of the specific objects, those objects can be accessed by reference only. Importantly, where the specific objects are data fields linked to a table in a database as managed by a container managed persistence (CMP) bean, an update to the table will not be required when the static analysis of the enterprise bean otherwise indicates that the data fields are merely accessed, but not updated.

Abstract: A method for calling a software method in a called CORBA application by a caller software method in a caller CORBA application in a process of a computer system is disclosed. The caller software method calls a software method in a CORBA stub sending a parameter which is created using a classloader of the caller application. The CORBA stub software method calls a software method in a dynamic proxy sending the parameter. The dynamic proxy software method calls an ORB sending the parameter. The ORB serializes the parameter and returns it to the dynamic proxy software method. The dynamic proxy software method calls the ORB sending the serialized parameter. The ORB deserializes the serialized parameter using a classloader of the called application and returns it to the dynamic proxy software method. The dynamic proxy software method calls the called software method sending the deserialized parameter.

Abstract: Memory management to support calls between objects in language environments support automatic garbage collection and language environments requiring explicit control of object destruction is provided. Reference counting is used to automatically control the lifetime of objects requiring explicit destruction and that are to be accessible across the language boundary. A data structure is maintained in a runtime component for each object that is accessed over a language boundary. The reference count for each non-garbage collected object is incremented by the runtime in accordance with the number of cross-language references held to it. When the count reaches zero through decrements as the references are returned and destroyed, the non-garbage collected object can be safely and automatically destroyed. The runtime creates a strong reference to any garbage collected object accessed by a cross-language call.

Abstract: A method and apparatus for subclassing System Object Model (SOM) class objects for a dynamic object-oriented language. A proxy class object is created using the dynamic language that points to the SOM class object. Next, a dynamic language subclass is created. This is followed by the creation of a SOM class object using the SOM interface, which causes certain SOM methods to be overridden by dynamic language redispatch stubs. The dynamic language overrides the SOM dispatch procedures and replaces the dispatcher with its own procedures. The new dispatch procedure will search for a method in the dynamic language class object method table first in response to a message, and if not found, redirects the message to the SOM environment.