Skip to content

ErrorEntity should be Serializable #178

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.

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

Closed
haqer1 opened this issue Feb 16, 2018 · 1 comment
Closed

ErrorEntity should be Serializable #178

haqer1 opened this issue Feb 16, 2018 · 1 comment
Assignees
Milestone

Comments

@haqer1
Copy link
Contributor

haqer1 commented Feb 16, 2018

ErrorEntity should be Serializable to avoid exceptions like the following in environments involving some remoting:
com.arangodb.ArangoDBException : Response: 409, Error: 1210 - unique constraint violated - in index 1355495 of type hash over ["email"]; conflicting key: 1355503 [Proxied because : Original exception caused: class java.io.NotSerializableException: com.arangodb.entity.ErrorEntity]

haqer1 added a commit to haqer1/arangodb-java-driver that referenced this issue Feb 16, 2018
@mvollmary mvollmary self-assigned this Feb 16, 2018
@mvollmary mvollmary added this to the 4.3.4 milestone Feb 16, 2018
@mvollmary
Copy link

Thanks for the feedback. Change will be in the next release.

mvollmary pushed a commit that referenced this issue Jun 14, 2018
…essary failures in src/test/java/com/arangodb/ArangoDBTest (#197)

* Fix-up for #178.

* Allow & account for pre-existing users other than ROOT to avoid unnecessary failures in src/test/java/com/arangodb/ArangoDBTest: fixes issue #196.

* Minor tweak.

* Minor simplification in initial users loop.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants