Class OwnLogCarryingMissingFileException
- java.lang.Object
-
- java.lang.Throwable
-
- java.lang.Exception
-
- com.mchange.v2.cfg.ConfigParseException
-
- com.mchange.v2.cfg.OwnLogCarryingMissingFileException
-
- All Implemented Interfaces:
java.io.Serializable
public class OwnLogCarryingMissingFileException extends ConfigParseException
Nothing was found at an identifier, reported by a source that has already made its own complete account of the absence — which is what "own log carrying" means, and what separates this from an ordinaryFileNotFoundException.Absence is normally reported for a source by whoever catches it, as a FINE "could not be found. Skipping." item. A source throws this instead when that generic item would be wrong or insufficient: because the absence deserves a louder level than FINE, or because it is not in fact being skipped. Catchers must therefore defer entirely to
ConfigParseException.getDelayedLogItems()and add nothing of their own, or the same absence gets reported twice, in two different voices.Concretely,
FileUrlPropertiesConfigSourcethrows this for all three states of itsrequiredoption: absent-and-required is a veto rather than a skip, absent underpermissions=useronlywithrequiredunstated warrants a WARNING rather than a FINE, and only an explicitrequired=falsegets the ordinary skip item — which it supplies itself, viaMConfig.skippingFileNotFoundDelayedItem(java.lang.String, java.lang.Exception).- See Also:
- Serialized Form
-
-
Constructor Summary
Constructors Constructor Description OwnLogCarryingMissingFileException(java.lang.String msg, java.lang.Throwable cause, java.util.List<DelayedLogItem> delayedLogItems)
-
Method Summary
-
Methods inherited from class com.mchange.v2.cfg.ConfigParseException
getDelayedLogItems
-
-
-
-
Constructor Detail
-
OwnLogCarryingMissingFileException
public OwnLogCarryingMissingFileException(java.lang.String msg, java.lang.Throwable cause, java.util.List<DelayedLogItem> delayedLogItems)
-
-