Bea Systems, Inc.

Oracle International Corporation

Salesforce Com, Inc.

Chris Fry

Sam Pullara

Craig David Weissman

Peter Morreli

Scott Ziegler

A database system includes servers configured to receive requests from user systems. Each server includes a local and a global store. Each local store stores the number of requests received by its server. The system includes a processor configured to receive the number of requests from servers. The processor is configured to determine the number of requests received by all of the servers, and send this number of requests to each server. The global store stores the number of requests received from the processor. A given server is configured to compare the number of requests received by the servers with a threshold number. If this number is greater than the threshold number, then the given server is configured to send a message to the user systems that the number of threshold requests has been exceeded and/or the given server will discontinue accepting requests.

Method and system for governing resource consumption in a multi-tenant system

A streaming parser API expands a base parser by building an iterative method on top of the base parser. The iterative method allows a user to pass a selected element type to the base parser, which can step through the XML document until it locates a matching element. The base parser can then extract the element, process the element as an event, and place the event on an event stream for use by an application.

Streaming parser API for processing XML document

A schema parser can be used in data binding to create a schema object model when given an XML schema. Java classes can be generated using the schema object model, which correspond to elements and types in the schema. Mapping can be done in each direction between the schema and Java classes, which can be written to a type mapping directory. The schema object model can also contain mappings between each Java class and an XSD type. The mappings in the type mapping directory can then be used to generate XML when given a Java object tree, and can be used to create and populate a Java class when given an XML instance matching the schema object model.

System and method for XML data binding

Improved XML transformation is obtained through the combined use of caching and pooling. A transformer caching pool can cache transformers to server client transformation requests. A transformer resource manager can select any appropriate transformer from the transformer caching pool. Once an appropriate transformer is selected, the resource manager can mark the transformer as busy and return it to the client. If a transformer is not available, the transformer resource manager can contact a transformer creator to create a new transformer and can then place the new transformer in the transformer caching pool. The new transformer can then be marked as busy and returned to the client to serve the transformation request.

System and method for fast XSL transformation

Transaction management systems can take advantage of a lightweight approach to conversation management. In a cluster, a conversation manager can be used to keep track of state location throughout the cluster. When a cluster computing device receives a request, that computing device can contact the conversation manager to determine the location of the state within the cluster. Once the conversation manager provides the computing device with the location of the state, the computing device can invoke the state for the conversation. All state information can be kept in-memory on computing devices in the cluster in order to improve performance. 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.

Systems and methods for lightweight conversations

Selective parsing of an XML document

Broad XML support is obtained through use of a set of streaming parser APIs. An application or client needing access to an XML document can contact an XML parser, XML processor, or XML reader in order to gain access to the document. The XML processor selects and instantiates a streaming parser API that is appropriate for the XML document and the client or application. Streaming parser APIs include raw streaming parser APIs, non-validating streaming parser APIs, and validating streaming parser APIs. The XML parser can then provide a variety of types of access to the application or client that does not require the entire document to be read into memory, including providing an XML stream, pulling XML information, and skipping unwanted XML from the document.

Growing community of inventors

Berkeley, CA, United States of America

Chris Fry