docs(temporal): Java EE / Jakarta EE edge-resolver spec + design + plan#94
Open
avfirsov wants to merge 3 commits into
Open
docs(temporal): Java EE / Jakarta EE edge-resolver spec + design + plan#94avfirsov wants to merge 3 commits into
avfirsov wants to merge 3 commits into
Conversation
Merges docs/java-ee-edge-resolvers.md (problem/corpus/priorities/acceptance) with the gortex integration design (FrameworkSynthesizer extract→resolve, contract reuse, layer-ownership table) and architecture-review fixes (InferImplements interface-only+repo-gated, Cartesian matcher, @Alternative/ @resource traps). Decisions D1–D4 resolved with rationale. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Buildable execution plan derived from docs/design/06-javaee-synthesizer.md: Phase 0 shared infra, A (EJB+CDI), B (REST/Servlet), C (JMS), D (XML descriptors), E (SOAP). Atomic tasks with file touch-points, edge tiers, tests, acceptance, sequencing, and risk gates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Friendly ping @zzet 🙂 — CI is green (9/9) and the branch is |
Owner
|
Hey @avfirsov, I prefer to keep the documents in English in the repository. As well as I have to think if such type of docs are necessary to have in git or better to have a different format. Problem with those docs that they have to be maintained (not outdated). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the Java EE / Jakarta EE edge-resolver design docs (no code):
docs/java-ee-edge-resolvers.md— the spec/ТЗ: problem (Java EE wires components declaratively via annotations/descriptors → ~30% lost edges on a large monolith), per-subsystem rules (JMS, EJB, REST, SOAP, Servlet, CDI), synthetic nodes, edge-origin classification, priorities, acceptance criteria + metrics.docs/design/06-javaee-synthesizer.md— how it maps onto gortex internals: theFrameworkSynthesizerextract→resolve split, layer-ownership table (EJB/CDI/JMS = synthesizerEdgeCalls; REST/SOAP = contract enrichmentEdgeMatches; filter-chain = ordered-edge pass),EdgeImplements/EdgeExtendssubtype resolution, contract-matcher reuse for cross-repo, confidence tiers, and settled decisions (ambiguity → hidden-speculative;@Resourcesignal-priority;@Alternative/@Specializes; audience viaMetaSpeculative).docs/design/07-javaee-implementation-plan.md— phased execution plan (0 shared infra, A EJB+CDI, B REST/Servlet, C JMS, D XML descriptors, E SOAP) with file touch-points, edge tiers, tests, sequencing and risk gates.Why
Captures the design + roadmap for closing gortex's Java EE blind spots (today Java symbols index via tree-sitter but CDI/EJB/JMS/JAX-RS dispatch edges are missing) so the implementation can land as reviewable, independently-shippable PRs. Grounded in the actual gortex synthesizer/contract machinery (file:line touch-points in §12 of doc 06).
Docs-only — no code changes.