Skip to content

Comments

ServiceContext utility class#273

Merged
namedgraph merged 5 commits intodevelopfrom
rf-proxy-config
Feb 18, 2026
Merged

ServiceContext utility class#273
namedgraph merged 5 commits intodevelopfrom
rf-proxy-config

Conversation

@namedgraph
Copy link
Member

Refactored configuration

namedgraph and others added 5 commits February 18, 2026 17:03
…ice`

`Service` is now a pure data interface (SPARQL endpoint URLs + credentials only),
no longer extending `RemoteService`. HTTP client/proxy infrastructure is moved into
the new `ServiceContext` class, which pairs a `Service` with its `Client`,
`MediaTypes`, `maxGetRequestSize`, and backend proxy URI.

- `lapp:frontendProxy` and `lapp:backendProxy` removed from RDF model; loaded
  from system-level config (`LDHC.frontendProxy`, `LDHC.backendProxy`) at startup
  and stored in a `serviceContextMap` in `Application`
- `Application.getServiceContext(Service)` looks up the `ServiceContext` for any
  `Service` at runtime
- All JAX-RS resources and filters obtain client/proxy access via
  `getSystem().getServiceContext(service).getX()`
- Import chain (`ImportExecutor`, `CSVGraphStore*`, `RDFGraphStoreOutput`,
  `StreamRDFOutputWriter`) receives `Service + Application system` (not
  `ServiceContext`) since they are plain Java objects, not HK2-managed beans
- `Application.ban(Resource, ...)` overload removed; all callers use the
  `ban(URI, ...)` form
- `core.model.Application.getService()` removed to avoid covariant return type
  clash after `ldh.Service` dropped `RemoteService`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@namedgraph namedgraph merged commit a33e665 into develop Feb 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant