Oracle International Corporation

Sun Microsystems, Inc.

Paul D Sandoz

Brian Goetz

John Robert Rose

Alexander R Buckley

Maurizio Cimadamore

Mark B Reinhold

Kohsuke Kawaguchi

Oleksiy Stashok

Santiago M Pericas-Geertsen

Alan Bateman

Chris Hegarty

Techniques for lowering Java try statements in a symbolic description language are disclosed, including: obtaining a set of Java source code; determining that the set of Java source code includes a try statement; and generating, based on the set of Java source code, a symbolic description language (SDL) model including a lowered SDL representation of the try statement. The lowered SDL representation of the try statement includes: a body including a set of basic SDL blocks; an exception region including (a) a subgraph of the set of basic SDL blocks and (b) an operation covered by the exception region; and a catch entry block, in the set of basic SDL blocks, that is declared as a successor block for when the operation covered by the exception region throws an exception.

Lowering Java try statements in a symbolic description language

Techniques for modeling Java source code in a symbolic description language are disclosed, including: obtaining a set of Java source code; determining that the set of Java source code includes a user-defined type; determining that the set of Java source code includes a loop; generating, based on the set of Java source code, a symbolic description language (SDL) model including an SDL representation of the user-defined type and an SDL representation of the loop.

Modeling java source code in a symbolic description language

Techniques for managing temporal dependencies between sets of foreign resources are disclosed, including: allocating, in a runtime environment, a segment of foreign memory to a first memory session, the runtime environment being configured to use a garbage collector to manage memory in a heap, and the foreign memory including off-heap memory that is not managed by the garbage collector; opening, in the runtime environment, a second memory session that descends from the first memory session; while the second memory session is open, encountering a request to close the first memory session; responsive to encountering the request to close the first memory session, determining that the first memory session has at least one open descendant memory session; responsive to determining that the first memory session has at least one open descendant memory session, declining the request to close the first memory session.

Managing temporal dependencies between sets of foreign resources

Techniques for managing lifecycles of sets of foreign resources are disclosed, including: opening, in a runtime environment configured to use a garbage collector to manage memory in a heap, a memory session; allocating a first subset of a set of foreign memory to a memory segment associated with the memory session, the foreign memory including off-heap memory that is not managed by the garbage collector; encountering, in the runtime environment, an instruction to close the memory session; responsive to encountering the instruction to close the memory session, deallocating the subset of the set of foreign memory.

Managing lifecycles of sets of foreign resources

Modular co-versioning may involve the creation of multi-version libraries that may include multiple versions of a class. A multi-version library may include a base version and one or more other versions each of which may correspond to a particular, respective version of a software development kit, runtime environment or software platform, according to various embodiments. At runtime, a multi-version library may be searched in order to load a version of a class that corresponds to the version of the currently executing runtime environment. If the multi-version library does not include a version of the class corresponding to the currently executing version of the environment/platform, a version of the class corresponding to a previous version of the environment may be loaded if found in the multi-version library. Alternatively, if no other version of the class is found, a base version of the class may be loaded from the multi-version library.

Modular co-versioning in a dynamically linked runtime environment

Techniques relating to fused objects are disclosed. Embodiments include verifying the validity of a transition from a current tail template to a new tail template for a fused object. The validity of the transition is determined by analyzing the type transitions per memory slot. If the type transition, for each memory slot, constitutes a type-compatible transition, then the transition from the current tail template to the new tail template is valid. If the type transition, for any memory slot, is not type-compatible, then the transition from the current tail template to the new tail template is not valid. Embodiments include generating a fused object with a repeating tail. A tail template associated with a fused object is repeated multiple times in the tail of the fused object.

Verifying the validity of a transition from a current tail template to a new tail template for a fused object

A fused object includes a head and a tail. A head template is not modifiable. A tail template is modifiable. Modifying a tail template includes verifying the validity of a transition from a current tail template to a new tail template. The validity of the transition is determined by analyzing the type transitions per memory slot. If the type transition, for each memory slot, constitutes a type-compatible transition, then the transition from the current tail template to the new tail template is valid. If the type transition, for any memory slot, is not type-compatible, then the transition from the current tail template to the new tail template is not valid. A fused object may be associated with a repeating tail. A tail template associated with a fused object is repeated multiple times in the tail of the fused object.

System and method for providing a binary encoding protocol as an alternative to markup language protocols for Web services. Embodiments may provide a Web services stack with a single API that supports a binary encoding protocol in addition to a markup language protocol. Embodiments may dynamically and transparently switch between the markup language protocol and the binary encoding protocol, for example for communications between servers and clients in a Web services network environment. An exemplary markup language is XML. An exemplary binary encoding protocol that may be used is WS-Fast, which may use Abstract Syntax Notation One (ASN.1) and a mapping from XML Schema to ASN.1 for on-the-wire binary messages. Some embodiments may be implemented as a Java Web services stack that implements WS-Fast as an alternative to XML, while still supporting XML and providing one API to both protocols.

Dynamic web services stack

A method for transmitting data that includes receiving a first request to open a first virtual channel, the first virtual channel associated with a TCP connection, and negotiating a first payload encoding scheme between a client and a server to use on the first virtual channel. The method further includes receiving a first frame from the client, the frame including a first channel-id associated with the first virtual channel and a first payload that includes a first datum encoded using the first payload encoding scheme. In addition, the method includes decoding the first payload to obtain a decoded first datum and processing the decoded first datum to obtain a second datum. The method additionally includes generating a second frame that includes the first channel-id and a second payload that includes the second datum encoded using the first payload encoding scheme, and sending the second frame to the client.

Growing community of inventors

Redwood City, CA, United States of America

Paul D Sandoz