"JDK15 Java平台核心库开发者指南（PDF）-2020年9月版"

需积分: 5 47 浏览量更新于2024-01-10 收藏 557KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

• Any other combination of arguments returns

UNDECIDED

. Deserialization continues,

and any remaining filters are run until the object is accepted or rejected. If there

are no other filters, the object is accepted.

Setting a Custom Filter as a Method

A custom filter can also be implemented as a method. The method reference is used

instead of an inline lambda expression.

The

dateTimeFilter

method that is defined in the following example is used by the

code sample in Setting a Custom Filter for an Individual Stream.

public class FilterClass {

static ObjectInputFilter.Status

dateTimeFilter(ObjectInputFilter.FilterInfo info) {

Class<?> serialClass = info.serialClass();

if (serialClass != null) {

return serialClass.getPackageName().equals("java.time")

? ObjectInputFilter.Status.ALLOWED

: ObjectInputFilter.Status.REJECTED;

}

return ObjectInputFilter.Status.UNDECIDED;

}

Example: Filter for Classes in the java.base Module

This custom filter, which is also implemented as a method, allows only the classes

found in the base module of the JDK. This example works with JDK 9 and later.

static ObjectInputFilter.Status

baseFilter(ObjectInputFilter.FilterInfo info) {

Class<?> serialClass = info.serialClass();

if (serialClass != null) {

return

serialClass.getModule().getName().equals("java.base")

? ObjectInputFilter.Status.ALLOWED

: ObjectInputFilter.Status.REJECTED;

}

return ObjectInputFilter.Status.UNDECIDED;

}

Built-in Filters

The Java Remote Method Invocation (RMI) Registry, the RMI Distributed Garbage

Collector, and Java Management Extensions (JMX) all have filters that are included

Chapter 2

Built-in Filters

2-8

in the JDK. You should specify your own filters for the RMI Registry and the RMI

Distributed Garbage Collector to add additional protection.

Filters for RMI Registry

Note:

Use these built-in filters as starting points only. Edit the

sun.rmi.registry.registryFilter

system property to configure blacklists

and/or extend the whitelist to add additional protection for the RMI Registry.

To protect the whole application, add the patterns to the

jdk.serialFilter

global system property to increase protection for other serialization users that

do not have their own custom filters.

The RMI Registry has a built-in whitelist filter that allows

objects to be bound in the registry. It includes instances

of the

java.rmi.Remote

java.lang.Number

java.lang.reflect.Proxy

java.rmi.server.UnicastRef

java.rmi.activation.ActivationId

java.rmi.server.UID

java.rmi.server.RMIClientSocketFactory

, and

java.rmi.server.RMIServerSocketFactory

classes.

The built-in filter includes size limits:

maxarray=1000000,maxdepth=20

Supersede the built-in filter by defining a filter using the

sun.rmi.registry.registryFilter

system property with a pattern. If the filter that

you define either accepts classes passed to the filter, or rejects classes or sizes,

the built-in filter is not invoked. If your filter does not accept or reject anything, the

built-filter is invoked.

Filters for RMI Distributed Garbage Collector

Note:

Use these built-in filters as starting points only. Edit the

sun.rmi.transport.dgcFilter

system property to configure blacklists

and/or extend the whitelist to add additional protection for Distributed

Garbage Collector. To protect the whole application, add the patterns to the

jdk.serialFilter

global system property to increase protection for other

serialization users that do not have their own custom filters.

The RMI Distributed Garbage Collector has a built-in whitelist filter that accepts

a limited set of classes. It includes instances of the

java.rmi.server.ObjID

java.rmi.server.UID

java.rmi.dgc.VMID

, and

java.rmi.dgc.Lease

classes.

The built-in filter includes size limits:

maxarray=1000000,maxdepth=20

Chapter 2

Built-in Filters

2-9

Supersede the built-in filter by defining a filter using the

sun.rmi.transport.dgcFilter

system property with a pattern. If the filter accepts

classes passed to the filter, or rejects classes or sizes, the built-in filter is not

invoked. If the superseding filter does not accept or reject anything, the built-filter

is invoked.

Filters for JMX

Note:

Use these built-in filters as starting points only. Edit the

jmx.remote.rmi.server.serial.filter.pattern

management property to

configure blacklists and/or extend the whitelist to add additional protection

for JMX. To protect the whole application, add the patterns to the

jdk.serialFilter

global system property to increase protection for other

serialization users that do not have their own custom filters.

JMX has a built-in filter to limit a set of classes allowed to be sent as a deserializing

parameters over RMI to the server. That filter is disabled by default. To enable

the filter, define the

jmx.remote.rmi.server.serial.filter.pattern

management

property with a pattern.

The pattern must include the types that are allowed to be sent as parameters over RMI

to the server and all types they depends on, plus

javax.management.ObjectName

and

java.rmi.MarshalledObject

types. For example, to limit the allowed set of classes

to Open MBean types and the types they depend on, add the following line to

management.properties file.

com.sun.management.jmxremote.serial.filter.pattern=java.lang.*;java.math

.BigInteger;java.math.BigDecimal;java.util.*;javax.management.openmbean.

*;javax.management.ObjectName;java.rmi.MarshalledObject;!*

Logging Filter Actions

You can turn on logging to record the initialization, rejections, and acceptances of

calls to serialization filters. Use the log output as a diagnostic tool to see what's being

deserialized, and to confirm your settings when you configure whitelists and blacklists.

When logging is enabled, filter actions are logged to the java.io.serialization

logger.

To enable serialization filter logging, edit the

$JDK_HOME/conf/logging.properties

file.

To log calls that are rejected, add

java.io.serialization.level = FINER

To log all filter results, add

java.io.serialization.level = FINEST

Chapter 2

Logging Filter Actions

2-10

used in documentation of deprecated APIs, for example, to describe the reason for

deprecation, and to suggest alternative APIs.

Note the capitalization: the annotation starts with an uppercase D and the Javadoc tag

starts with a lowercase d.

Using the @Deprecated Annotation

To indicate deprecation, precede the module, class, method, or member declaration

with @Deprecated. The annotation contains these elements:

• @Deprecated(since="

– <version> is the version when the API was deprecated. This is for

informational purposes. The default is the empty string (

• @Deprecated(forRemoval=

)

– forRemoval=true indicates that the API is subject to removal in a future

release.

– forRemoval=false recommends that code should no longer use this API;

however, there is no current intent to remove the API. This is the default value.

For example: @Deprecated(since="9", forRemoval=true)

The @Deprecated annotation causes the Javadoc-generated documentation to be

marked with one of the following, wherever that program element appears:

• Deprecated.

• Deprecated, for removal: This API element is subject to removal in a future

version.

The

javadoc

tool generates a page named deprecated-list.html which contains

the list of deprecated APIs, and adds a link in the navigation bar to that page.

The following is a simple example of using the @Deprecated annotation from the

java.lang.Thread class:

public class Thread implements Runnable {

...

@Deprecated(since="1.2")

public final void stop() {

...

}

...

Semantics of Deprecation

The two elements of the @Deprecated annotation give developers the opportunity to

clarify what deprecation means for their exported APIs.

For the JDK platform:

• @Deprecated(forRemoval=true) indicates that the API is eligible to be

removed in a future release of the JDK platform.

• @Deprecated(since="

") contains the JDK version string that

indicates when the API element was deprecated, for those deprecated in JDK

9 and beyond.

Chapter 3

How to Deprecate APIs

3-2

剩余91页未读，继续阅读

weixin_40191861_zj

粉丝: 68
资源: 1万+

会员权益专享

"JDK15 Java平台核心库开发者指南（PDF）-2020年9月版"

JDK 12 Documentation - Java Core Libraries Developer Guide

JDK16-java-core-libraries-developer-guide.pdf

JDK17-java-core-libraries-developer-guide.pdf

bcprov-jdk14-145.jar

单元测试报错 NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi. 该怎么办

3、安装和配置JDK rpm -qa|grep openjdk packages中jdk-8u211-linux-x64.tar.gz cd /opt/packages tar -zxvf jdk-8u211-linux-x64.tar.gz -C /opt/programs vi /etc/profile export JAVA_HOME=/opt/programs/jdk1.8.0_211 export PATH=$PATH:$JAVA_HOME/bin source /etc/profile java -version写注释

JAVA_OPTS="$JAVA_OPTS --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED" 这个参数怎么设置

NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED

jdk-8.0.302.8-hotspot和jdk1.8区别

aspose-words-19.3-jdk17.jar-java

bcprov-jdk16-1.46.jar has unsigned entries - org/bouncycastle/LICENSE.class

picked up jdk_java_options: --add-opens=java.base/java.lang=all-unnamed --add-opens=java.base/java.io=all-unnamed --add-opens=java.base/java.util=all-unnamed --add-opens=java.base/java.util.concurrent=all-unnamed --add-opens=java.rmi/sun.rmi.transport=all-unnamed

.\nihao\Java\jdk-17.0.7\bin\java.exe -jar .\nihao\GearsNetworkPacket-1.0-SNAPSHOT-1-full.jar

note: picked up jdk_java_options: --add-opens=java.base/java.lang=all-unnamed --add-opens=java.base/java.io=all-unnamed --add-opens=java.base/java.util=all-unnamed --add-opens=java.base/java.util.concurrent=all-unnamed --add-opens=java.rmi/sun.rmi.transport=all-unnamed

-Djava.ext.dirs=/usr/local/jdk-18.0.2.1/jre/lib/ext:/root/rocketmq/rocketmq-4.9.2/bin/../lib:/usr/local/jdk-18.0.2.1/lib/ext i

note: picked up jdk_java_options: --add-opens=java.base/java.lang=all-unnamed --add-opens=java.base

JDK14-java-core-libraries-developer-guide.pdf

会员权益专享

最新资源