Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
1.9.0
-
None
-
None
Description
Problem
With the current version of 1.9.0-SNAPSHOT (as of 9th of April 2019) the java compiler generates broken code under 2 circumstances:
- Type A (e.g. foo.A) references Type B from a different namespace (e.g. bar.B)
- Both types fulfill the criteria of SpecificCompiler.isCustomCodable(..)
This generates code where foo.A is generated with a protected customCode(...) which calls out to bar.B's protected customCode(...). This breaks as A cannot access B's protected methods.
Possible solutions
- Change the isCustomCodeable criteria in such a way that it fails for namespace-crossing type-references
- Open up access to customCode/customDecode. This may expose internals though.
Attachments
Issue Links
- is duplicated by
-
AVRO-2386 Generated code doesn't compile, because customDecode and customEncode are protected
- Resolved