public class GspNotActivatedException extends IllegalStateException
This build fails explicitly rather than returning a wrong answer. An earlier design silently deleted a statement from every parse, so an unlicensed user got plausible but incomplete results. That is worse than a refusal in every direction that matters: it is indistinguishable from a parser bug, it corrupts downstream lineage and impact analysis without anyone noticing, and it costs the vendor the support calls too. Supportability wins over covertness.
Extends IllegalStateException so existing callers that already
handle unchecked failures from parse() keep working.
GspRuntime.activate(byte[]),
Serialized Form| Modifier and Type | Method and Description |
|---|---|
String |
auditId()
Correlates this refusal with the GSP_ENTITLEMENT_REFUSED log line.
|
GspActivation |
getActivation()
The activation state that caused the refusal, for logging and support.
|
String |
reasonCode()
Stable machine-readable reason, e.g.
|
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toStringpublic GspActivation getActivation()
public String reasonCode()
EXPIRED, MISSING.