Abstract: A resource registry provides nondeterministic operation environment affording flexible access for resource execution and status monitoring on the cloud. The resource registry service provides generic resource management utilizing registration, updating, and unregistration by resource providers. A requester for an operation may register in the resource registry, an operation resource having parameters defined in metadata. The resource registry notifies a registered resource listener of this registration of the operation resource. The resource listener may then execute the operation according to parameters defined in the operation resource. The resource listener returns a response to the resource registry, concerning a result of execution of the operation. The resource registry updates this status in the metadata of the operation resource. The requester is then able to look up the operation resource's metadata to determine current status of the operation.

Abstract: An operation execution request is created by an operation requester at an operations service module. The operation execution request is stored by the operations service module. A polling message for the operation execution request is received. The polling message includes a name of an operation. A response including the operation execution request and corresponding operation data is returned. An execution service schedules internally the operation for execution. The execution service sends an acknowledgement message to acknowledge the operation execution request. The operation data and corresponding operation execution request is locked for execution by other execution services. The execution service executes the operation with the operation data and provides result of the operation execution. The operations service module updates status of the operation execution request. The updated status is provided to the operation requester upon polling for status of the operation execution request.

Abstract: A resource registry provides nondeterministic operation environment affording flexible access for resource execution and status monitoring on the cloud. The resource registry service provides generic resource management utilizing registration, updating, and unregistration by resource providers. A requester for an operation may register in the resource registry, an operation resource having parameters defined in metadata. The resource registry notifies a registered resource listener of this registration of the operation resource. The resource listener may then execute the operation according to parameters defined in the operation resource. The resource listener returns a response to the resource registry, concerning a result of execution of the operation. The resource registry updates this status in the metadata of the operation resource. The requester is then able to look up the operation resource's metadata to determine current status of the operation.

Abstract: Various embodiments of systems and methods for automated test framework for testing enterprise services consumer technologies are described. According to one aspect, an enterprise service client is generated based on the WSDL document of an enterprise service. The generation of the client includes generation of source code files and other client artifacts. The client artifacts are compiled and the client is configured to connect to the server system hosting the enterprise service. Real test data is loaded into a non-persistent memory and executed against the server system of the enterprise system. If no exception occurs, the test call is assumed successful. If the test calls to this enterprise service are successful, the service is marked as compatible with the different clients that performed the test calls.

Abstract: Various embodiments of systems and methods for automated test framework for testing enterprise services consumer technologies are described. According to one aspect, an enterprise service client is generated based on the WSDL document of an enterprise service. The generation of the client includes generation of source code files and other client artifacts. The client artifacts are compiled and the client is configured to connect to the server system hosting the enterprise service. Real test data is loaded into a non-persistent memory and executed against the server system of the enterprise system. If no exception occurs, the test call is assumed successful. If the test calls to this enterprise service are successful, the service is marked as compatible with the different clients that performed the test calls.

Abstract: A system and method are provided to generate a generic object access model. In one embodiment, web services data types are detected. The web services data types are determined as simple types or complex types. Generic objects are generated to find first Java types for the complex types.

Abstract: A system and method are provided to generate a dynamic web services invocation model. In one embodiment, a first metadata and a second metadata are extracted from description content of a Web Service Definition Language (WSDL) file. The first metadata and the second metadata are inspected. A web service is invoked via a dynamic web services invocation model.

Abstract: A system and method are provided to generate an enhanced configuration model. In one embodiment, application programming interfaces (APIs) are identified. The APIs relate to web services and/or web services clients. Access to the APIs is provides via a configuration model.

Abstract: A method and system for generating schema to Java descriptors. In one embodiment, a second object having customized schema to Java mapping information is created. The second object is placed within a first object. Via the first object, schema to Java generation is initiated.

Abstract: A method and system for container-based configuration and administration. In one embodiment, a configuration file is created at a first location. The configuration file is duplicated into a duplicate configuration file, which is placed at a second location.

Abstract: A method and system for creating a common model. In one embodiment, a web services model and a web service client model are identified. The web services and web services client models are then unified to create a common model.

Abstract: A method and system for generating schema to Java mapping description. In one embodiment, default schema to Java mapping information is customized into customized schema to Java mapping information. An object having the customized mapping information is created, and schema to Java generation is initialized via the object.

Abstract: A method and system for directly mapping web services interfaces and Java interfaces. In one embodiment, default mapping information is identified, the default mapping information having default interface mapping information and default schema to Java mapping information. The default mapping information is then update and a mapping descriptor having the updated mapping information is generated. The updated information contains updated interface mapping information and updated schema to Java mapping information.

Abstract: A method and system for unifying configuration files. In one embodiment, a web services configuration file and a web services client configuration file are identified. The web services and web services client configuration files are unified to create a configuration file.

Abstract: A system and method for the lifecycle of a protocol processing a message is described. In one embodiment, in a stateless object-oriented runtime environment, an instance of a reliable messaging protocol is used to process a message. The processing including receiving a message and performing operations based on said message.

Abstract: A method is described that involves processing a Web services message within an object oriented runtime environment. The processing involves executing a plurality of protocols to support a Web service that the message pertains to. Each one of the protocols perform one or more operations that contribute to a different part of the processing. The executing involves a first of the protocols receiving from an object WS Addressing information retrieved from the message's header. The executing also involves the first protocol providing the WS Addressing information to a second of the protocols. The executing also involves the second protocol providing the WS Addressing information to at least one of: a third protocol of the protocols; a component that performs an endpoint method of said Web service; software that identifies a new transport level destination address for said message.

Abstract: A system and method for the lifecycle of a protocol processing a message is described. In one embodiment, a stateless protocol instance is registered with an objected-oriented environment and a stateless protocol context instance is invoked to process a message.

Abstract: A method is described that involves converting elements of a textual Web services message body into object oriented tokens with a first token reader. The first token reader sends the object oriented tokens to a dispatching token reader. The method also involves performing the following at the dispatching token reader for each token of the tokens: checking if the token is to be processed by another token reader; forwarding the token to an object oriented representation of the Web services message body if the checking does not identify another token reader; forwarding the token to another token reader if the checking does identify another token reader.

Abstract: A method is described that involves comprising, during runtime in an object-oriented environment, invoking, from an object, a first Web services endpoint method to process a first message by: invoking the first Web services endpoint method through a first interface according to an endpoint method invocation format, where, the first Web services endpoint method is implemented with a first component that is provided one or more services by a first container. The method also involves invoking, from the object, a second Web services endpoint method to process a second message by: invoking the second Web services endpoint method through a second interface according to the endpoint method invocation format. The second Web services endpoint method is implemented with a second component that is provided one or more services by a second container. The first and second containers have respective interfaces that are different.

Abstract: A method is described that involves processing a Web services message within an object oriented runtime environment. The processing itself involves executing a plurality of protocols to support a Web service that the message pertains to. Each one of the protocols perform one or more operations that contribute to a different part of the processing. The executing is hibernated by storing state information of the protocols externally from the protocols. The executing is resumed by loading the saved state information back into the protocols. The executing includes one of the protocols performing the following: receiving from an object information retrieved from the message's header; and, providing at least a portion of the information to another protocol amongst the plurality of protocols.