Optional clearly expresses intentions and reduces code noise for null judgments. 1. Optional.ofNullable is a common way to deal with null objects. For example, when taking values ??from maps, orElse can be used to provide default values, which makes the logic clearer and more concise; 2. Use chain calls maps to achieve nested values, safely avoid NPE, and automatically terminate if any link is null and return the default value; 3. Filter can be used for conditional filtering, and subsequent operations will continue to be performed only if the conditions are met, otherwise it will jump directly to orElse, which is suitable for lightweight business judgment; 4. It is not recommended to overuse Optional, such as basic types or simple logic, which will increase complexity. It is more appropriate to directly return null or throw exceptions in some scenarios.
Using Java Optional is actually much more useful than you think.

Many people think Optional is a "decoration" that prevents null pointers, but when you are really using it in a project, you will find that it not only makes the code clearer, but also helps you avoid many potential bugs. Let’s take a look at how to use Optional through several actual scenarios.
1. Optional.ofNullable
is the most commonly used entry
Optional.ofNullable
is the most common practice when dealing with objects that may be null. For example, take the value from the map:

Map<String, String> userMap = getUserMap(); String name = Optional.ofNullable(userMap.get("name")) .orElse("default_name");
The advantage of writing this way is that it is clear logic: if the key exists, use it, and if it does not exist, give a default value. The code is much simpler than judging null first and then assigning values.
Note: If you are sure that the object is not empty, you can use
Optional.of()
, but if null is passed, an exception will be thrown directly, so it is safer to useofNullable
most of the time.
2. Chained calls make nested values ??more elegant
Sometimes we need to take out a certain attribute from an object chain, such as user.getAddress().getCity()
. At this time, it is easy to cause NPE because a certain level in the middle is null.
Rewrite it with Optional:
String city = Optional.ofNullable(user) .map(User::getAddress) .map(Address::getCity) .orElse("unknown");
This method avoids null layer by layer and makes the logic clearer. Each .map()
takes the value "safely" down. Once any of the links are null, the entire chain will automatically terminate and eventually return the default value you specified.
3. Use filter
for conditional screening to avoid redundant judgments
Optional can also be used with filter, for example, we want to check whether the username starts with "admin":
Optional<String> usernameOpt = Optional.ofNullable(getUsername()); String result = usernameOpt.filter(u -> u.startsWith("admin")) .map(u -> "Admin User: " u) .orElse("Not admin");
The filter in this example plays a role in filtering in advance. Only when the conditions are met will the map be executed, otherwise it will jump directly to orElse. This writing method is particularly suitable for lightweight business judgments.
4. Overuse of Optional is not recommended
Although Optional is convenient, don't abuse it. For example, when a method returns a basic type (int, boolean, etc.), Java provides an exclusive Optional type such as OptionalInt
, but if you simply return an int, there is no need to go around Optional.
In addition, in some scenarios, it is more appropriate to directly return null or throw exceptions. Optional is not the master key to solve all null problems.
Basically that's it. The core value of Optional is to express intentions and reduce the noise of null judgments, rather than forcibly stuffing all logic into it. If you use it skillfully, the code will be very comfortable to read.
The above is the detailed content of Java Optional example. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The rational use of semantic tags in HTML can improve page structure clarity, accessibility and SEO effects. 1. Used for independent content blocks, such as blog posts or comments, it must be self-contained; 2. Used for classification related content, usually including titles, and is suitable for different modules of the page; 3. Used for auxiliary information related to the main content but not core, such as sidebar recommendations or author profiles. In actual development, labels should be combined and other, avoid excessive nesting, keep the structure simple, and verify the rationality of the structure through developer tools.

When you encounter the prompt "This operation requires escalation of permissions", it means that you need administrator permissions to continue. Solutions include: 1. Right-click the "Run as Administrator" program or set the shortcut to always run as an administrator; 2. Check whether the current account is an administrator account, if not, switch or request administrator assistance; 3. Use administrator permissions to open a command prompt or PowerShell to execute relevant commands; 4. Bypass the restrictions by obtaining file ownership or modifying the registry when necessary, but such operations need to be cautious and fully understand the risks. Confirm permission identity and try the above methods usually solve the problem.

There are three main differences between Callable and Runnable in Java. First, the callable method can return the result, suitable for tasks that need to return values, such as Callable; while the run() method of Runnable has no return value, suitable for tasks that do not need to return, such as logging. Second, Callable allows to throw checked exceptions to facilitate error transmission; while Runnable must handle exceptions internally. Third, Runnable can be directly passed to Thread or ExecutorService, while Callable can only be submitted to ExecutorService and returns the Future object to

Javaprovidesmultiplesynchronizationtoolsforthreadsafety.1.synchronizedblocksensuremutualexclusionbylockingmethodsorspecificcodesections.2.ReentrantLockoffersadvancedcontrol,includingtryLockandfairnesspolicies.3.Conditionvariablesallowthreadstowaitfor

Java's class loading mechanism is implemented through ClassLoader, and its core workflow is divided into three stages: loading, linking and initialization. During the loading phase, ClassLoader dynamically reads the bytecode of the class and creates Class objects; links include verifying the correctness of the class, allocating memory to static variables, and parsing symbol references; initialization performs static code blocks and static variable assignments. Class loading adopts the parent delegation model, and prioritizes the parent class loader to find classes, and try Bootstrap, Extension, and ApplicationClassLoader in turn to ensure that the core class library is safe and avoids duplicate loading. Developers can customize ClassLoader, such as URLClassL

The key to Java exception handling is to distinguish between checked and unchecked exceptions and use try-catch, finally and logging reasonably. 1. Checked exceptions such as IOException need to be forced to handle, which is suitable for expected external problems; 2. Unchecked exceptions such as NullPointerException are usually caused by program logic errors and are runtime errors; 3. When catching exceptions, they should be specific and clear to avoid general capture of Exception; 4. It is recommended to use try-with-resources to automatically close resources to reduce manual cleaning of code; 5. In exception handling, detailed information should be recorded in combination with log frameworks to facilitate later

Polymorphism is one of the core features of Java object-oriented programming. Its core lies in "one interface, multiple implementations". It implements a unified interface to handle the behavior of different objects through inheritance, method rewriting and upward transformation. 1. Polymorphism allows the parent class to refer to subclass objects, and the corresponding methods are called according to the actual object during runtime; 2. The implementation needs to meet the three conditions of inheritance relationship, method rewriting and upward transformation; 3. It is often used to uniformly handle different subclass objects, collection storage and framework design; 4. When used, only the methods defined by the parent class can be called. New methods added to subclasses need to be transformed downward and accessed, and pay attention to type safety.

Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity
