System and method for deploying a web service

• US 7,693,955 B2
• Filed: 02/13/2003
• Issued: 04/06/2010
• Est. Priority Date: 02/22/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Karakashian, Todd
• Primary Examiner(s): Vaughn, Jr.; William C
• Assistant Examiner(s): Shingles; Kristie D
• Application Number:
  US10/366,246
• Publication Number:
  US 20040045005A1
• Time in Patent Office: 2,609 Days
• Field of Search: 709/200, 709/220, 709/222, 709/201, 709/217, 709/203, 717/120
• US Class Current: 709/217
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A Web service can be deployed using a backend component such as an Enterprise JavaBean or Java class. The operation of the Web service can be mapped to methods of the backend component. An interceptor can provide access to SOAP contents of a Web service invocation message, passing contents to and from the backend component. The interceptor writes response data received from the backend component to a Web service response message, which can be sent to the client invoking the Web service. A codec, such as a serializer or deserializer, can be used to convert data in the Web service invocation message and invocation response message between XML representations and Java objects for use with the backend component.

Claims

1. A system for deploying a web service, comprising:

a backend component for implementing a web service, the operation of the web service being mapped to methods of the backend component;

a registered inbound interceptor adapted to process an inbound message before the backend component and a registered outbound interceptor adapted to process an outbound message after the backend component;

a codec for converting data in the inbound message and the outbound message between Extensible Markup Language (XML) representations and objects for use with said backend component;

an autotyper for generating an additional codec, the additional codec converting additional data types from XML representation to JAVA objects; and

wherein the backend component, the registered inbound and the registered outbound interceptors, the codec and the autotyper are contained within a web service container; and

wherein the system includes at least one processor.

2. A system according to claim 1, further comprising a Java Message Service (JMS) connection factory for using JMS with the web service.

3. A system according to claim 1, wherein said backend component is selected from the group consisting of beans, JMS message consumers, JMS message producers, and classes.

4. A system according to claim 1, further comprising a container driver to interact with the registered interceptors and the backend component.

5. A system according to claim 1, further comprising a web service home page for describing the web service.

6. A system according to claim 1, further comprising a thin client for accessing the web service from a virtual machine.

7. A method for deploying a web service, comprising:

deploying a backend component for implementing the web service;

providing access to SOAP contents of web service messages using a registered inbound interceptor adapted to process an inbound message before the backend component and a registered outbound interceptor adapted to process an outbound message after the backend component;

providing a codec for converting data in the web service invocation message from an XML representation to an object for use with the backend component implementing the web service;

an autotyper for generating an additional codec, the additional codec converting additional data types from XML representation to objects; and

wherein the backend component, the registered inbound and the registered outbound interceptors, the codec and the autotyper are contained within a web service container; and

wherein the generation of the additional codec is done using at least one processor.

8. A method according to claim 7, further comprising:

mapping the operation of the web service mapped to methods of the backend component.

9. A method according to claim 7, further comprising:

reading the web service messages with the interceptor and passing the contents of the message to the backend component.

10. A method according to claim 7, further comprising:

receiving response data from the backend component and writing SOAP contents to a web service response message using the interceptor.

11. A method according to claim 10, further comprising:

providing a codec for converting data in the web service response message from a object to an XML representation.

12. A method according to claim 7, further comprising:

implementing data types for the web service.

13. A method according to claim 7, further comprising:

using a SOAP message processor to process SOAP information not encoded in the backend component.

14. A method according to claim 7, further comprising:

editing a web service deployment descriptor to activate the web service.

15. A method according to claim 7, further comprising:

generating a web service home page to describe the web service.

16. A method according to claim 7, further comprising:

generating a client for accessing the web service from a virtual machine.

17. A method according to claim 16, further comprising:

generating a client jar to contain the client.

18. A method according to claim 7, further comprising:

packaging and deploying a web service archive file.

19. A system for deploying a web service, comprising:

means for deploying a backend component for implementing the web service;

means for providing access to SOAP contents of web service messages using a registered inbound interceptor adapted to process an inbound message before the backend component and a registered outbound interceptor adapted to process an outbound message after the backend component;

means for providing a codec for converting data in the web service messages from an XML representation to an object for use with the backend component implementing the web service;

an autotyper that can generate an additional codec, the additional codec converting additional data types from XML representation to objects; and

wherein the backend component, the registered inbound and the registered outbound interceptors, the codec and the autotyper are contained within a web service container; and

wherein the system includes at least one processor.

20. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

deploy a backend component for implementing the web service;

provide access to SOAP contents of web service messages using a registered inbound interceptor adapted to process an inbound message before the backend component and a registered outbound interceptor adapted to process an outbound message after the backend component;

provide a codec for converting data in the web service messages from an XML representation to an object for use with the backend component implementing the web service;

an autotyper that can generate an additional codec, the additional codec converting additional data types from XML representation to objects; and

wherein the backend component, the registered inbound and the registered outbound interceptors, the codec and the autotyper are contained within a web service container.

21. A computer readable storage medium containing code comprising:

a code segment including instructions to deploy a backend component for implementing the web service;

a code segment including instructions to provide access to SOAP contents of web service messages using a registered inbound interceptor adapted to process an inbound message before the backend component and a registered outbound interceptor adapted to process an outbound message after the backend component;

a code segment including instructions to provide a codec for converting data in the web service messages from an XML representation to an object for use with the backend component implementing the web service;

an autotyper that can generate an additional codec, the additional codec converting additional data types from XML representation to objects; and

wherein the backend component, the registered inbound and the registered outbound interceptors, the codec and the autotyper are contained within a web service container.