[
https://issues.apache.org/jira/browse/AVRO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776499#action_12776499
]
Doug Cutting commented on AVRO-164:
-----------------------------------
AVRO-185 fixes this by adding the protocol to generated interfaces.
After that's committed, Paranamer will only needed for reflection, where method
parameter names are unknown. If we wanted to remove paranamer even there, then
I suppose we could simply name parameters by their type, e.g., foo(String
title, String body) would become foo(String string1, String string2).
> Generate paranamer metadata for interfaces as part of SpecificCompiler
> ----------------------------------------------------------------------
>
> Key: AVRO-164
> URL: https://issues.apache.org/jira/browse/AVRO-164
> Project: Avro
> Issue Type: Improvement
> Components: java
> Reporter: Philip Zeyliger
>
> As discussed a bit in AVRO-146, we shouldn't need to run paranamer in a
> separate build step if we have all the schema information already. We could
> keep the code paths the same across the reflected and specific use cases by
> simply generating the necessary paranamer variable in SpecificCompiler.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
