2nd/10_Wiki/Dev/Topic_Java/Java_Encapsulation.md

id, title, category, status, verification_status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, created_at, updated_at, review_reason, merge_history, tags, raw_sources, applied_in, github_commit

id	title	category	status	verification_status	canonical_id	aliases	duplicate_of	source_trust_level	confidence_score	created_at	updated_at	review_reason	merge_history	tags	raw_sources	applied_in	github_commit
java-encapsulation	Java Encapsulation	Programming_Language	draft	conceptual		getters and setters 자바 캡슐화		B	0.9	2026-07-04	2026-07-04			java programming w3schools oop encapsulation getters-setters	https://www.w3schools.com/java/java_encapsulation.asp

Java Encapsulation

🎯 한 줄 통찰 (One-line insight)

Get/set methods give control beyond simple read/write access — the source explicitly notes you can make an attribute read-only (get method only, no set) or write-only (set method only, no get), a flexibility that direct public-field access can never provide. [S1]

🧠 핵심 개념 (Core concepts)

• Encapsulation — hiding sensitive data from users by (1) declaring attributes private and (2) providing public get/set methods. [S1]
• Naming convention — get/set prefix + capitalized variable name (getName(), setName()). [S1]
• Getter — returns the private variable's value. [S1]
• Setter — takes a parameter and assigns it via this.field = param;. [S1]
• Read-only/write-only design — omit the setter for read-only, omit the getter for write-only. [S1]

📖 세부 내용 (Details)

• Private field with getter/setter: private String name; public String getName() { return name; } public void setName(String newName) { this.name = newName; }. [S1]
• Direct access fails: myObj.name = "John"; // error: name has private access in Person. [S1]
• Correct access via encapsulation: myObj.setName("John"); System.out.println(myObj.getName()); // "John". [S1]
• Benefits listed: better control over attributes/methods, read-only/write-only capability, flexibility to change internals without affecting other code, increased data security. [S1]

⚖️ 모순 및 업데이트 (Contradictions & updates)

소스에서 모순되는 정보는 발견되지 않음.

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — private 필드 + get/set 메서드는 데이터 보호의 표준 설계 패턴이다. [S1]

💻 코드 패턴 (Code patterns)

Private field with getter/setter encapsulation (Java):

public class Person {
    private String name; // private = restricted access
    public String getName() {
        return name;
    }
    public void setName(String newName) {
        this.name = newName;
    }
}

✅ 검증 상태 및 신뢰도

• 상태: draft
• 검증 단계: conceptual
• 출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
• 신뢰 점수: 0.90
• 중복 검사 결과: 신규 생성 (New discovery)

🔗 지식 그래프 (Knowledge Graph)

• 상위/루트: Java Tutorial
• 관련 개념: Java Modifiers, Java This Keyword, Java Packages
• 참조 맥락: private 필드 보호 원칙 — Packages 챕터로 이어짐.

📚 출처 (Sources)

• [S1] W3Schools — Java Encapsulation — https://www.w3schools.com/java/java_encapsulation.asp

📝 변경 이력 (Change history)

• 2026-07-04: Initial draft synthesized from the W3Schools "Java Encapsulation" page (Astra wiki-curation, P-Reinforce v3.1 format).