DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
41 lines
1.8 KiB
Markdown
41 lines
1.8 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: adapter-inbound-graphql-c07
|
|
title: 파싱·검증 실패의 와이어 형식은 이 플랫폼이 정하지 않는다
|
|
topic: schema-and-wire-models
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:adapter-inbound-graphql-c07
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: adapter-inbound-graphql-c07
|
|
file: ../../../final/evidence/rendered/adapter-inbound-graphql-c07.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/adapter-inbound-graphql-c07.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/16-adapter-inbound-graphql.md#L604 이다.
|
|
module: adapter-inbound-graphql
|
|
---
|
|
|
|
# 파싱·검증 실패의 와이어 형식은 이 플랫폼이 정하지 않는다
|
|
|
|
`GraphQlRequestErrorMapper`의 진단은 정확하지만 배선된 것은 리졸버 쪽뿐이다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
`GraphQlRequestErrorMapper`의 javadoc이 자기 존재 이유를 적는다. 진단이 정확하고, 배선된 것은 리졸버 쪽(`GraphQlExceptionResolver`, autoconf=4)뿐이다. 파싱·검증 실패의 와이어 형식을 이 플랫폼이 정하지 않는다는 뜻이다.
|
|
|
|
## GraphQlRequestErrorMapper 참조 위치
|
|
|
|
:::evidence key="adapter-inbound-graphql-c07" alt="코드베이스에서 GraphQlRequestErrorMapper 를 검색한 출력 6줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="GraphQlRequestErrorMapper 코드베이스 검색 — 6줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 플랫폼이 거부하는 실패는 안정 코드로 매핑된다
|
|
|
|
`runtime/GraphQlWireErrorMapper`(autoconf=4)와 `runtime/GraphQlPlatformRejectionMapper`(main_other=3)가 배선돼 있어 익명 연산, 복잡도 초과 등은 안정 코드로 매핑된다. 덮이지 않는 것은 graphql-java 자신이 만드는 구문/검증 오류다.
|
|
|
|
<!-- body:end -->
|