Web services programming and deployment

• US 20040045005A1
• Filed: 02/13/2003
• Published: 03/04/2004
• 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
• Granted Patent: US 7,693,955 B2
• Time in Patent Office: Days
• US Class Current: 719/310
• 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.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

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;

an interceptor for providing access to SOAP contents of a Web service invocation message, said interceptor adapted to read the Web service invocation message and pass the contents of the message to said backend component, said interceptor adapted to receive response data from the backend component and write SOAP contents to a Web service response message; and

a codec for converting data in the Web service invocation message and invocation response message between XML representations and Java objects for use with said backend component.

2. A system according to claim 1, further comprising a 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 Enterprise JavaBeans, JMS message consumers, JMS message producers, and Java classes.

4. A system according to claim 1, further comprising an Autotyper for generating additional codecs.

5. A system according to claim 1, further comprising a container driver for controlling the flow of the Web service invocation message.

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

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

8. A method for deploying a Web service, comprising:

deploying a backend component for implementing the Web service;

providing access to SOAP contents of a Web service invocation message using an interceptor; and

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

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

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

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

reading the Web service invocation message with the interceptor and passing the contents of the message to the backend component.

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

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

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

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

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

implementing data types for the Web service.

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

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

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

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

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

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

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

generating a Java client for accessing the Web service from a Java virtual machine.

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

generating a client jar to contain the Java client.

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

packaging and deploying a Web service archive file.

20. A computer-readable medium, comprising:

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

means for providing access to SOAP contents of a Web service invocation message using an interceptor; and

means for providing a codec for converting data in the Web service invocation message from an XML representation to a Java object for use with the backend component implementing the Web service.

21. A computer program product for execution by a server computer for deploying a Web service, comprising:

computer code for deploying a backend component for implementing the Web service;

computer code for providing access to SOAP contents of a Web service invocation message using an interceptor; and

computer code for providing a codec for converting data in the Web service invocation message from an XML representation to a Java object for use with the backend component implementing the Web service.

22. 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 a Web service invocation message using an interceptor; and

means for providing a codec for converting data in the Web service invocation message from an XML representation to a Java object for use with the backend component implementing the Web service.

23. 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 a Web service invocation message using an interceptor; and

provide a codec for converting data in the Web service invocation message from an XML representation to a Java object for use with the backend component implementing the Web service.

24. A computer data signal embodied in a transmission medium, 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 a Web service invocation message using an interceptor; and

a code segment including instructions to provide a codec for converting data in the Web service invocation message from an XML representation to a Java object for use with the backend component implementing the Web service.