Should use Map instead of Hashtable

문서 > 코드 분석 > Static Analysis Rules > Should use Map instead of Hashtable

이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

Metadata

ID: java-best-practices/replace-hashtable-with-map

Language: Java

Severity: Warning

Category: Best Practices

Description

If your application does not require thread safety, it is recommended to use the modern java.util.Map interface instead of java.util.Hashtable.

Map offers efficient implementations like HashMap, which offer greater flexibility and faster execution. If thread safety is needed, you can opt for ConcurrentHashMap, which maintains thread safety while still adhering to modern coding practices associated with Map.

Non-Compliant Code Examples

public class Foo {
    void bar() {
        Hashtable hashtable1 = new Hashtable(); // consider using java.util.Map instead
        Hashtable<String, Integer> hashtable2 = new Hashtable<>();
    }
}

Compliant Code Examples

public class Foo {
    void bar() {
        Map<String, Integer> h = new HashMap<>();
    }
}