Recurrence not Serializable
See original GitHub issueIs there a specific reason to keep the Recurrence
class not serializable?
In my Project sometimes just the Recurrence is stored in a database.
For that hibernate needs the serialization.
If there is no specific reason, I offer you to make a PR to change this. 😉
I saw that a few classes already get it on #75, but are mixed with test fixes. Those classes might become changes as well if necessary.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
NotSerializableException in Java with Examples
In Java, a NotSerializableException exception is thrown when an instance of a class must implement the Serializable interface. The exception is ...
Read more >Infinite Recursion with Jackson JSON and Hibernate JPA issue
For Jackson to work well, one of the two sides of the relationship should not be serialized, in order to avoid the infite...
Read more >Recurrence (Oracle Fusion Middleware Java API Reference for ...
Serializable, java.lang.Cloneable. public final class Recurrence extends oracle.odi.domain.support. ... No public constructors are available in this class.
Read more >TypeError: can not serialize 'Composed' object #2001 - GitHub
On Sentry after deploying the ddtrace upgrade, immediately got: TypeError: can not serialize 'Composed' object. This looks like a recurrence ...
Read more >Recurrence (Escenic Content Engine 7.5.12-2 API documentation)
Creates a copy of another recurrence. Parameters: pRecurrence - the recurrent to copy; can not be null . Throws: java.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
From my perspective, this whole library, in essence, is already a serialization/deserialization tool. Using Java serialization rather than the standardized ical serialization is ill-advised, as it is guaranteed to be less space/time efficient, and simply muddles the purpose of this library. Also it means that your database would only be interoperable with Java, rather than any language which supports parsing ical properties.
+1 for property scribes -1 for
Serializable
.@Poeschl Oh nice, glad you figured it out! 😸