Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify serialization strategy behavior #54

Closed
henri-tremblay opened this issue Jun 19, 2017 · 0 comments
Closed

Clarify serialization strategy behavior #54

henri-tremblay opened this issue Jun 19, 2017 · 0 comments
Assignees
@henri-tremblay
Labels
enhancement
Milestone
2.6

Comments

@henri-tremblay
Copy link
Contributor

So far, Objenesis was behaving differently depending on the instantiator picked. We should

  • Describe an accepted default behaviour
  • Improve the TCK to test this default

The accepted default is

  • Fail if the class isn't serializable
  • Call the first non-serializable constructor in the hierarchy otherwise
  • No special behaviour for Externalizable classes
  • No serializable specific method called (e.g. readResolve, readExternal, readObject, readObjectNoData)
@henri-tremblay henri-tremblay added this to the 2.6 milestone Jun 19, 2017
@henri-tremblay henri-tremblay self-assigned this Jun 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@henri-tremblay henri-tremblay

Labels
enhancement
Projects
None yet
Milestone
2.6
Development

No branches or pull requests
1 participant
@henri-tremblay