| Web services runtime architecture -> Monitor Keywords |
|
|
 
Web services runtime architectureRelated Patent Categories: Electrical Computers And Digital Processing Systems: Multicomputer Data Transferring, Computer Conferencing, Priority Based MessagingWeb services runtime architecture description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20070150546, Web services runtime architecture. Brief Patent Description - Full Patent Description - Patent Application Claims
CLAIM OF PRIORITY [0001] This application is a Continuation of and claims priority to U.S. patent application Ser. No. 10/366,236, filed Feb. 13, 2003, entitled "WEB SERVICES RUNTIME ARCHITECTURE," which application claims priority to U.S. Provisional Patent Application No. 60/359,098, filed Feb. 22, 2002, entitled "WEB SERVICES RUNTIME ARCHITECTURE," as well as U.S. Provisional Patent Application No. 60/359,231, filed Feb. 22, 2002, entitled "WEB SERVICES PROGRAMMING AND DEPLOYMENT," each of which is hereby incorporated herein by reference. COPYRIGHT NOTICE [0002] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document of the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. FIELD OF THE INVENTION [0003] The present invention relates to the implementation of web services. BACKGROUND [0004] Web services are becoming an integral part of many application servers, with an importance that can rival HTTP or RMI stacks. Java standards for Web services are being developed through the Java Community Process. Businesses are building important applications on top of Web services infrastructures, such as is available in WebLogic Server from BEA Systems of San Jose, Calif. Presently, however, there is no complete implementation of Web services upon which to build. BRIEF SUMMARY [0005] A system and method in accordance with the present invention overcome deficiencies in the prior art by utilizing a runtime architecture for Web services. A container driver is used in the architecture for accepting an invoke request for Web services, such as from a protocol adapter. The container driver can perform any data binding and unbinding required to process the invoke request, utilizing a plugin component such as a Java binding codec, SOAP codec, XML codec, or custom codecs. [0006] An interceptor can receive the context information for the invoke request from the container driver and modify the message context to be used with Web services. An invocation handler can receive the context information from the container driver after the message context has been modified by the interceptor. The invocation handler can pass parameters from the message context to the target of the request and process values returned from the target. The invocation handler can then pass these values to the container driver, such that the container driver can formulate a response to the invoke request. The response and message context can then be returned to the client or protocol adapter. [0007] Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0008] FIG. 1 is a diagram of a system in accordance with one embodiment of the present invention. [0009] FIG. 2 is a diagram of a Web service container that can be used with the system of FIG. 1. [0010] FIG. 3 is a diagram of a Web service client that can be used with the system of FIG. 1. [0011] FIG. 4 is a flow chart of a method fo the present invention. DETAILED DESCRIPTION [0012] Systems and methods in accordance with one embodiment of the present invention can overcome deficiencies in existing Web service implementations by providing a more stable, complete implementation that is suitable as an application integration platform. [0013] A Web services architecture can allow for communication over a number of transports/protocols. HTTP can continue to be a primary transport mechanism for existing applications, while transport mechanisms such as SMTP, FTP, JMS, and file system mailboxes can also be supported. [0014] Message formats such as SOAP 1.1 and 1.2 with attachments can be used as primary message formats. It is also possible to accept Web service requests that are XML-encoded and submitted via HTTP posts. A Web services architecture can support plugging in other message formats and provide a mechanism for access to the raw message for user code. [0015] A Web services architecture can utilize a stack that supports a standards-based default binding of fundamental XML data types supported in various Web service platforms. An API can be used to allow other binding mechanisms to be plugged in. The binding to be used can be specified on a per-operation basis. [0016] Various security and messaging standards require a context or state to be associated with Web service messages. A Web services architecture can support the processing of multiple message contexts, such as those related to security or conversation ID, and can offer user code access to these contexts. Many of these contexts can be encoded into a SOAP header, although it is also possible to include the contexts in the underlying protocol layer (e.g., cookies in HTTP) or in the body of the message (e.g., digital signatures). A Web services container can explicitly process contexts associated with planned security features for Web services. [0017] A Web services stack can support a number of dispatch and synchrony models. Dispatch to both stateless and stateful components can be supported, using both remote procedure call (RPC) and messaging invocation semantics. Synchronous and asynchronous processing of requests can also be supported. In particular, it can be possible to enqueue an incoming message, to enqueue an outbound message, and to make asynchronous outbound calls. Enqueuing involves downloading files, one at a time, from a queue. Continue reading about Web services runtime architecture... Full patent description for Web services runtime architecture Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Web services runtime architecture patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Web services runtime architecture or other areas of interest. ### Previous Patent Application: System and method for providing an information service to distribute real-time information to users via a presence system Next Patent Application: Multi-measurement vortex flowmeter Industry Class: Electrical computers and digital processing systems: multicomputer data transferring or plural processor synchronization ### FreshPatents.com Support Thank you for viewing the Web services runtime architecture patent info. IP-related news and info Results in 0.29624 seconds Other interesting Feshpatents.com categories: Accenture , Agouron Pharmaceuticals , Amgen , AT&T , Bausch & Lomb , Callaway Golf 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
