[
https://issues.apache.org/jira/browse/AVRO-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009523#comment-13009523
]
Scott Carey commented on AVRO-784:
----------------------------------
Looking good.
We'll need to create a different velocity profile instead of breaking the
current one (perhaps 'bean' instead of 'classic'?) and figure out how to wire
this up to switch types at user request in the Tool/AntTask/MavenPlugin.
I'd like to see some name collision tests too. We can have collisions with
Object.getClass(), IndexedRecord.getSchema(), and perhaps others. Those will
need to be mangled. I believe "class" should already be mangled at the field
name level (see SpecificCompiler.mangle()).
The mangling for method names will differ from mangling for field names.
Currently, a field named "volatile" gets mangled to be a member variable named
"volatile$". The getter can be getVolatile() rather than getVolatile$().
Conversely, "schema" does not need to have its field mangled, but does need to
have its getter mangled. Its setter does not require mangling, but for
consistency should be.
> SpecificCompiler should generate accessors
> ------------------------------------------
>
> Key: AVRO-784
> URL: https://issues.apache.org/jira/browse/AVRO-784
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.5.0
> Reporter: E. Sammer
> Labels: features
> Attachments: avro-784.diff, avro-784.diff
>
>
> Avro's Java SpecificCompiler should generate java bean style accessors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
