Oracle International Corporation

Sun Microsystems, Inc.

Oracle America, Inc.

Nec Research Institute, Inc.

Mark B Reinhold

Alexander R Buckley

Alan Bateman

Jonathan J Gibbons

Chris Hegarty

Mandy Chung

Paul Sandoz

Karen M P Kinnear

Brian Goetz

Peter B Kessler

Harold S Stone

Paul D Sandoz

Lai Hung Mandy Chung

Mandy L Chung

Duncan Stuart Ritchie

Majd F Sakr

Alan E Bateman

Techniques for identifying permitted illegal access operations in a module system are disclosed. An operation, expressed in a first module, that attempts to access a module element of a second module is identified. Based on a module declaration associated with the second module, the module element is determined inaccessible to the first module. Additionally or alternatively, based on an access modifier associated with the module element, the module element is determined inaccessible to the operation. The operation is determined as an illegal access operation. The illegal access operation is permitted to access the module element. A warning corresponding to the illegal access operation is generated.

Identifying permitted illegal access operations in a module system

A bridge module is generated to bridge standard modules in a module system and non-module code in a non-module system. The bridge module includes explicit dependencies associated with a namespace, such as a dependency path corresponding to the non-module code. The bridge module exposes packages of the non-module code at least to the standard modules. Operations are performed on a code base that uses standard modules, bridge modules, and non-module code.

Composing a module system and a non-module system

Techniques for managing split packages in a module system are disclosed. A code conflict exists between two packages, in different modules, based at least in part on the packages being named identically and including executable code. No code conflict exists between two other identically-named packages, in different modules, based at least in part on the packages not including any executable code. Managing split packages may be based, at least in part, on module membership records associated with the modules.

Managing split packages in a module system

Access to a module element within a first module by a second module is prohibited if the module element within the first module has not been exposed to the second module. If a particular module element within a first module has been exposed to a second module, then access to the particular module element by the second module may or may not be allowed depending on: (a) whether the particular module element has been declared with a public or non-public access modifier, (b) whether a second exposed module element, which includes the particular module element, has been declared with a public or non-public access modifier, (c) a level of access associated with the operation that attempts to access the particular module element of the first module, and/or (d) whether an accessibility override configuration is set for accessing the particular module element.

Restrictive access control for modular reflection

Permissive access control for modular reflection

A serial form of a serializable exposed first module element of a module in a module system is analyzed. An unexposed and/or inaccessible second module element expressed in the serial form is identified as a potential error condition. A corrective execution is executed and/or a warning is presented.

Modular serialization

Bridging a module system and a non-module system

The disclosed embodiments provide a system that facilitates the development and maintenance of a software program. This system includes a software development kit (SDK) and a runtime system for the software program. During operation, the system associates classes of the software program with module declarations for a set of modules and uses the module declarations to manage dependencies in the software program throughout the life cycle of the software program.

Polyphasic modules for software development

Some embodiments provide a system that facilitates the development, maintenance, and execution of a software program. During operation, the system obtains a module declaration for a module to be used in the software program. Next, the system resolves one or more dependencies of the module using the module declaration and a list of available modules for the software program. Finally, the system uses the resolved dependencies to manage the software program throughout the life cycle of the software program.

Dependency resolution in polyphasic modules

The disclosed embodiments provide a system that provides access control for a software program. During operation, the system identifies a member of a module to be used in the software program. Next, the system infers the visibility of the member based on the accessibility of the member. Finally, the system uses the visibility and the accessibility to provide access control during the life cycle of the software program.

Access control in modules for software development

The disclosed embodiments provide a system that facilitates the compilation of a software program. During operation, the system uses a directory hierarchy for the software program to infer a compilation unit to be used in the software program as a member of a module. Next, the system obtains a module declaration for the module using the directory hierarchy. Finally, the system enables compilation of the software program by dynamically identifying and locating one or more dependencies of the module using the module declaration and the directory hierarchy.

Compile-time management of polyphasic modules

A mechanism is disclosed for compiling a program which is written in a first language having a first syntax. An indication is detected, in a set of code within the program, that the set of code contains a non-compliant identifier that is not intended to be compliant with the first syntax associated with the first language. In response to detecting the indication, the non-compliant identifier is transformed into a transformed identifier that is compliant with a second syntax associated with a second language. Compiled code that uses and operates with the transformed identifier is emitted. For example, the first program may be written in language that is substantially similar to the Java programming language. The first syntax may be a syntax that is substantially compliant with syntax of the Java programming language. The second language may be XML, wherein the second syntax is substantially compliant with XML.

Mechanism for compiling programs

A method and apparatus for providing selective object locking is provided. First, a lock object is designated. The identity of the lock object is then made available to objects in an object calling hierarchy. The first object invoked by the calling thread obtains a lock on the lock object to protect data associated with the first invoked object. Other objects in the object calling hierarchy can relock the lock object to protect their data. The invention also provides for selective object locking by providing the capability for a calling thread to specify that no object locking is to be preformed, which causes objects invoked by the calling thread to not perform object locking.

Growing community of inventors

Menlo Park, CA, United States of America

Mark B Reinhold