docs(10_Wiki): 위키 구조 정리 — 언어 튜토리얼 카테고리 폴더 제거 + 신규 자산 동기화

Topic_CSS/Topic_HTML/Topic_JavaScript/Topic_Prompt/Topic_Comfyui 등 기존 카테고리 폴더를 정리하고,
Topic_Graphic/Dev 등 신규 산출물과 Topics 내부 세션/메모리 기록을 동기화.
This commit is contained in:
Antigravity Agent
2026-07-05 00:10:59 +09:00
parent a397bc4720
commit 1cfd3bbb56
1495 changed files with 68534 additions and 27 deletions
@@ -0,0 +1,76 @@
---
id: java-encapsulation
title: "Java Encapsulation"
category: "Programming_Language"
status: "draft"
verification_status: "conceptual"
canonical_id: ""
aliases: ["getters and setters", "자바 캡슐화"]
duplicate_of: ""
source_trust_level: "B"
confidence_score: 0.9
created_at: 2026-07-04
updated_at: 2026-07-04
review_reason: ""
merge_history: []
tags: ["java", "programming", "w3schools", "oop", "encapsulation", "getters-setters"]
raw_sources: ["https://www.w3schools.com/java/java_encapsulation.asp"]
applied_in: []
github_commit: ""
---
# [[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):
```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).