You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The class DocHandlerFactory offers a conveniente system to load and register type handler, but if even just one type handler is not found, the load process will fail.
It would be better if it was possible to tag handlers entry as "unsafe" (in which case the factory creations should not safe if the handler is not found).
fugerit79
changed the title
[fj-dpc-base] Handling of unsafe type handlers for DocHandlerFactory
[fj-doc-base] Handling of unsafe type handlers for DocHandlerFactory
Feb 26, 2023
fugerit79
changed the title
[fj-doc-base] Handling of unsafe type handlers for DocHandlerFactory
[fj-doc-base] Managing of unsafe DocTypeHandler for DocHandlerFactory
Feb 26, 2023
+ [Managing of unsafe DocTypeHandler for
DocHandlerFactory](#31)
+ update fj-core version to 0.8.13 (DocHandlerFactory would not work
with previous versions)
The class DocHandlerFactory offers a conveniente system to load and register type handler, but if even just one type handler is not found, the load process will fail.
It would be better if it was possible to tag handlers entry as "unsafe" (in which case the factory creations should not safe if the handler is not found).
Imagine the last handler is not available in class loader. Thi can be handled with the new properties :
unsafe="true" unsafeMode="log-trace"
The stack trace will be logged only if you set unsafeMod to log-trace. If you want to suppress the stack trace use :
unsafe="true" unsafeMode="log-message"
The text was updated successfully, but these errors were encountered: