Deprecated API
Contents
-
Deprecated MethodsMethodDescriptionUse
RuntimeReflection.register(Field...)instead. ParametersfinalIsWritableandallowUnsafeAccessno longer serve a purpose.UseRuntimeReflection.register(Field...)instead. ParameterfinalIsWritableno longer serves a purpose.UseRuntimeSerialization.register(Class[])instead. All possible custom constructors will be registered automatically.in 25.1 without replacement. This method is inherently unsafe as it can interfere with other code.OptionValuesshould be read-only. If the value of an option needs to be altered after options are set, then the new value should be stored in the language's context or instrument fields and read from there.If a file system was previously set useallowIO(IOAccess.newBuilder().fileSystem(fileSystem).build()).useContext.Builder.allowHostClassLookup(Predicate)instead.UseFileSystem.allowInternalResources(FileSystem)instead when migrating code that only reads internal resources. The replacement exposes internal resources and language homes through a read-only view. Code that needs mutable files based on internal resources should copy the resources to an application-controlled location, for example withEngine.copyResources(Path, String...), and expose that location through its configuredfileSystem.UseFileSystem.allowInternalResources(FileSystem)instead to expose language homes and other internal resources through a read-only view.useSource.getReader(),Source.getCharacters()orSource.getBytes()instead. The implementation is inefficient and can not distinguish byte and character based sources.useSourceSection.getCharacters()instead.
-
Deprecated Constructors