Layered ClassLoader issues #27
Replies: 3 comments 2 replies
-
Hi @lordofthejars thanks for feedback Do you know if also library (like Jackson) had the same problem ? |
Beta Was this translation helpful? Give feedback.
-
Hi @lordofthejars thanks for valuable feedback Serialization seemed to me the best way to both clone and persist data ( also on file system ). However I've implemented the Serializer outer the standard serialisation mechanism and the instantiation is explicit (not using the lookup in classoladers). This approach requires bit of code but is safe and controlled. I'm adding the possibility to serialise in different format (eg. Json) using third-party library. Deep-Copy could be an interesting alternative just in case |
Beta Was this translation helpful? Give feedback.
-
Are you using last version ? Could you share more infos ? (eg. Stacktrace ) Anyway I'm making serialisation strategy customisable ( ref. last SNAPSHOT ) |
Beta Was this translation helpful? Give feedback.
-
Hi, I opened an issue in the Quarkus project about one problem I faced during the serialization process, and it seems that the problem is widely extended to any project that can use a layered ClassLoader (quarkusio/quarkus#43111 (comment))
I know that reworking this might be complicated here, but it is an issue that might be raised in the future.
Beta Was this translation helpful? Give feedback.
All reactions