| commit | 6436f8301e4e7473c79b9570a2103c28b3d90482 | [log] [tgz] |
|---|---|---|
| author | Mark Struberg <struberg@apache.org> | Mon Jan 31 08:32:43 2022 +0100 |
| committer | Mark Struberg <struberg@apache.org> | Mon Jan 31 08:32:43 2022 +0100 |
| tree | c0d2c0da45ff362cfc2b2352273c3293a50e9409 | |
| parent | 86fa17f48a8c1edd4e0a2d5be8d6c0dc82f9c40d [diff] |
BATCHEE-156 only log a warning on CNFE There is one use case which might be ok: If someone works with different implementations, e.g. different JPA providers then the Exceptions might be different depending on implementations. In that case the batch developer might want to add Exceptions from all the supported implementations. And of course only one of them is available at runtime in that case. The other enlisted classes will likely throw a NCFE.