Abstract: A method and system for processing Web service messages within an object oriented runtime environment is described. In one embodiment, the method includes steps for invoking a single instance of a state-less protocol for processing inbound and outbound flows of Web services messages. After determining Web services messages have been received out of order, processing of the outbound flow of any remaining messages is suspended until a complete set of messages is received. The messages are rearranged into proper order before completing processing of the outbound flows of the remaining messages.

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

Abstract: An Web service (WS) archive is described. The archive includes components that define and describe the deployable WS such as the implementation classes of the WS, the WSDL of the WS, and descriptors that provide more detail than what is described in a normal WSDL that are specific to the WS of the archive.

Abstract: A method and system for processing Web service messages within an object oriented runtime environment is described. In one embodiment, the method includes steps for invoking a single instance of a state-less protocol for processing inbound and outbound flows of Web services messages. After determining Web services messages have been received out of order, processing of the outbound flow of any remaining messages is suspended until a complete set of messages is received. The messages are rearranged into proper order before completing processing of the outbound flows of the remaining messages.

Abstract: A method and system for implementing Web service built-in endpoints is described. In one embodiment, the system includes a built-in endpoint manager interface and a built-in endpoint implementation container.

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 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 processing also involves identifying a message key within the message and using the message key to identify an endpoint method for the message. The method also involves executing the endpoint method to generate a response message to the message.

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 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, 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 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 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 method and system for implementing Web service built-in endpoints is described. In one embodiment, the system includes a built-in endpoint manager interface and a built-in endpoint implementation container.

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