Abstract: A context framework allows context propagation over synchronous invocation and asynchronous invocation. A context carrier is created for each thread. A set of application programming interfaces allow software components to store and retrieve context entries. By referring to the context carrier and creating a new context carrier when a new thread is started, context can flow both upstream and downstream along the invocation chain.

Abstract: An apparatus, system, and method are disclosed for facilitating dynamic modification of existing software objects defined in a strongly-typed programming language. The apparatus includes an invocation framework, an embedder, a reference component, and a development reference component. The invocation framework is configured to pass a loosely-typed base object between a source component and a destination component. The embedder embeds a business object within the base object. The business object is defined at least in part by a type definition having a set of attributes and a name value uniquely associating the type definition to the business object. The reference component references the base object such that typing requirements of the business object are not explicitly enforced in a runtime environment. The development reference component references the type definition within a development environment such that typing for the business object is fixed during source code development and deployment.

Abstract: A method, apparatus, system, and signal-bearing medium that in an embodiment receive a specification of a method in a container-managed persistence bean and a specification of a procedure in a backend data store, generate code in a helper class associated with the container-managed persistence bean, determine a connector based on a connection factory type, and access the procedure via a backend-specific protocol and the connector. The code in the helper class performs the accessing. In this way, the container-managed persistence bean may access the backend data store without knowledge of the backend-specific protocol.

Abstract: A method, apparatus, system, and signal-bearing medium that in an embodiment receive a key parameter from a container-managed persistent bean, determine that the container-managed persistent bean is associated with a non-relational data store, creating a web service input message with the key parameter, and invoke a web service function with the web service input message to interface with a non-relational data store. The determination that the container-managed persistent bean is associated with a non-relational data store may be based on deployment description extension settings specified by a bean assembler. In this way, a container-managed persistent bean may be used to access a non-relational data store.